Answer in brief
CVE-2026-72487 records a Unknown severity vulnerability in PCI: Check ROM header and data structure addr before accessing. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=47b975d234eac39f3a72e5496d5f6158d8b806d1 <cd5b242d5848369b9e957340a7e30adee7b6763d || >=47b975d234eac39f3a72e5496d5f6158d8b806d1 <4997873e3abbad47a9e1e4abd05f045f77a74f22 || >=47b975d234eac39f3a72e5496d5f6158d8b806d1 <724042f8f98d2594b9d164549fd4292c6bd58120 || >=47b975d234eac39f3a72e5496d5f6158d8b806d1 <1d495446ec7ace5b61da366ffb161ee8319dd9a2 || >=47b975d234eac39f3a72e5496d5f6158d8b806d1 <721ad5b72448b5065ed309017ab563205f162404 || >=47b975d234eac39f3a72e5496d5f6158d8b806d1 <538796b807fcfb81b2ce40cc97a614fd8588feb5 | cd5b242d5848369b9e957340a7e30adee7b6763d, 4997873e3abbad47a9e1e4abd05f045f77a74f22, 724042f8f98d2594b9d164549fd4292c6bd58120, 1d495446ec7ace5b61da366ffb161ee8319dd9a2, 721ad5b72448b5065ed309017ab563205f162404, 538796b807fcfb81b2ce40cc97a614fd8588feb5 |
| Linux/Linuxgeneric | 4.5 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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]
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72487 records a Unknown severity vulnerability in PCI: Check ROM header and data structure addr before accessing. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=47b975d234eac39f3a72e5496d5f6158d8b806d1 <cd5b242d5848369b9e957340a7e30adee7b6763d || >=47b975d234eac39f3a72e5496d5f6158d8b806d1 <4997873e3abbad47a9e1e4abd05f045f77a74f22 || >=47b975d234eac39f3a72e5496d5f6158d8b806d1 <724042f8f98d2594b9d164549fd4292c6bd58120 || >=47b975d234eac39f3a72e5496d5f6158d8b806d1 <1d495446ec7ace5b61da366ffb161ee8319dd9a2 || >=47b975d234eac39f3a72e5496d5f6158d8b806d1 <721ad5b72448b5065ed309017ab563205f162404 || >=47b975d234eac39f3a72e5496d5f6158d8b806d1 <538796b807fcfb81b2ce40cc97a614fd8588feb5 | cd5b242d5848369b9e957340a7e30adee7b6763d, 4997873e3abbad47a9e1e4abd05f045f77a74f22, 724042f8f98d2594b9d164549fd4292c6bd58120, 1d495446ec7ace5b61da366ffb161ee8319dd9a2, 721ad5b72448b5065ed309017ab563205f162404, 538796b807fcfb81b2ce40cc97a614fd8588feb5 |
| Linux/Linuxgeneric | 4.5 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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]
Quoted source text, attributed separately from HOL analysis.