cveboard RSS feed

CVE-2026-72487

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2026
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

PCI: Check ROM header and data structure addr before accessing

In the Linux kernel, the following vulnerability has been resolved: PCI: Check ROM header and data structure addr before accessing We meet a crash when running stress-ng on x86_64 machine: BUG: unable to handle page fault for address: ffa0000007f40000 RIP: 0010:pci_get_rom_size+0x52/0x220 Call Trace: <TASK> pci_map_rom+0x80/0x130 pci_read_rom+0x4b/0xe0 kernfs_file_read_iter+0x96/0x180 vfs_read+0x1b1/0x300 Our analysis reveals that the ROM space's start address is 0xffa0000007f30000, and size is 0x10000. Because of broken ROM space, before calling readl(pds), the pds's value is 0xffa0000007f3ffff, which is already pointed to the ROM space end, invoking readl() would read 4 bytes therefore cause an out-of-bounds access and trigger a crash. Fix this by adding image header and data structure checking. We also found another crash on arm64 machine: Unable to handle kernel paging request at virtual address ffff8000dd1393ff Mem abort info: ESR = 0x0000000096000021 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x21: alignment fault The call trace is the same with x86_64, but the crash reason is that the data structure addr is not aligned with 4, and arm64 machine report "alignment fault". Fix this by adding alignment checking. [bhelgaas: shorten function names, wrap comments]

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
47b975d234eac39f3a72e5496d5f6158d8b806d1affectedgitcd5b242d5848369b9e957340a7e30adee7b6763dUnavailableNone listed
47b975d234eac39f3a72e5496d5f6158d8b806d1affectedgit4997873e3abbad47a9e1e4abd05f045f77a74f22UnavailableNone listed
47b975d234eac39f3a72e5496d5f6158d8b806d1affectedgit724042f8f98d2594b9d164549fd4292c6bd58120UnavailableNone listed
47b975d234eac39f3a72e5496d5f6158d8b806d1affectedgit1d495446ec7ace5b61da366ffb161ee8319dd9a2UnavailableNone listed
47b975d234eac39f3a72e5496d5f6158d8b806d1affectedgit721ad5b72448b5065ed309017ab563205f162404UnavailableNone listed
47b975d234eac39f3a72e5496d5f6158d8b806d1affectedgit538796b807fcfb81b2ce40cc97a614fd8588feb5UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
4.5affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver4.5UnavailableNone listed
6.1.178unaffectedsemverUnavailable6.1.*None listed
6.6.145unaffectedsemverUnavailable6.6.*None listed
6.12.97unaffectedsemverUnavailable6.12.*None listed
6.18.40unaffectedsemverUnavailable6.18.*None listed
7.1.5unaffectedsemverUnavailable7.1.*None listed
7.2unaffectedoriginal_commit_for_fixUnavailable*None listed