diff options
| author | Sean Nyekjaer <sean@geanix.com> | 2023-10-16 14:21:58 +0200 |
|---|---|---|
| committer | Steve Sakoman <steve@sakoman.com> | 2023-10-25 04:51:00 -1000 |
| commit | d4bc6a9374cedfe6e1e1ed0aa14985548d524819 (patch) | |
| tree | 69782127fd3e16dd80931d45e81112bde9b453bf /scripts/pybootchartgui/pybootchartgui.py | |
| parent | 9954a4df00884fcd76e60bb0a809670625c92454 (diff) | |
| download | poky-d4bc6a9374cedfe6e1e1ed0aa14985548d524819.tar.gz | |
dmidecode: fixup for CVE-2023-30630
The previous CVE-2023-30630_1.patch picked only the patch
"dmidecode: Write the whole dump file at once" d8cfbc808f.
But there was a refactoring which does not allow to cherry-pick it fast
forward. Resolving this conflict was not correctly done. The patch was:
+ u32 len;
+ u8 *table;
...
- if (!(opt.flags & FLAG_QUIET))
- pr_comment("Writing %d bytes to %s.", crafted[0x05],
- opt.dumpfile);
- write_dump(0, crafted[0x05], crafted, opt.dumpfile, 1);
+ dmi_table_dump(crafted, crafted[0x05], table, len);
It looks like the variables len and table have been added without
initialization.
Now this problem is solved by applying the previous refactoring as
well. Patch 1 gets replaced by Patch 1a and Patch 1b. Patch 2..4 are
rebased without changes.
This is basically the same patch as in kirkstone:
ea069a94a2 dmidecode: fixup for CVE-2023-30630
(From OE-Core rev: 0bc69dc078c39381a39789d3c5fff673d7da994c)
Signed-off-by: Sean Nyekjaer <sean@geanix.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'scripts/pybootchartgui/pybootchartgui.py')
0 files changed, 0 insertions, 0 deletions