CVE-2026-72487
CVE CVE-2026-72487EUVD EUVD-2026-59386Published 2026-08-15T05:57:23.000ZLast changed 2026-08-17T05:44:48.000ZCVSS 7.7
What the advisory describes
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]
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 47b975d234eac39f3a72e5496d5f6158d8b806d1 <4997873e3abbad47a9e1e4abd05f045f77a74f22; 47b975d234eac39f3a72e5496d5f6158d8b806d1 <724042f8f98d2594b9d164549fd4292c6bd58120; 47b975d234eac39f3a72e5496d5f6158d8b806d1 <cd5b242d5848369b9e957340a7e30adee7b6763d; patch: 6.18.40; patch: 7.1.5; 47b975d234eac39f3a72e5496d5f6158d8b806d1 <721ad5b72448b5065ed309017ab563205f162404; 4.5; patch: 7.2; patch: 6.1.178; 47b975d234eac39f3a72e5496d5f6158d8b806d1 <538796b807fcfb81b2ce40cc97a614fd8588feb5; 47b975d234eac39f3a72e5496d5f6158d8b806d1 <1d495446ec7ace5b61da366ffb161ee8319dd9a2; patch: 6.6.145; patch: 6.12.97; patch: 0
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.