CVE-2026-72487

HIGHPre-NVD 7.77.7—
EchelonGraph scoreHIGH confidence

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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: 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]

CVSS v3
7.7
EG Score
7.7(high)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity77% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (6)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

PCI: Check ROM header and data structure addr before accessing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cd5b242d5848369b9e957340a7e30adee7b6763d
generic

PCI: Check ROM header and data structure addr before accessing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/724042f8f98d2594b9d164549fd4292c6bd58120
generic

PCI: Check ROM header and data structure addr before accessing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/721ad5b72448b5065ed309017ab563205f162404
generic

PCI: Check ROM header and data structure addr before accessing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/538796b807fcfb81b2ce40cc97a614fd8588feb5
generic

PCI: Check ROM header and data structure addr before accessing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4997873e3abbad47a9e1e4abd05f045f77a74f22
generic

PCI: Check ROM header and data structure addr before accessing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d495446ec7ace5b61da366ffb161ee8319dd9a2

Vendor Advisories for CVE-2026-72487(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 31× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 02:34 UTCEG score recompute
  2. 2026-08-21 02:33 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 15:11 UTCGHSA enrichment
  5. 2026-08-20 03:52 UTCEG score recompute
  6. 2026-08-20 03:52 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 16:32 UTCGHSA enrichment
  9. 2026-08-19 05:12 UTCGHSA enrichment
  10. 2026-08-18 17:50 UTCEG score recompute
  11. 2026-08-18 17:50 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 06:18 UTCGHSA enrichment
  15. 2026-08-17 18:59 UTCEG score recompute
  16. 2026-08-17 18:58 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:27 UTCEG score recompute
  19. 2026-08-17 06:27 UTCGHSA enrichment
  20. 2026-08-17 05:57 UTCEG score recompute▲ 7.70
  21. 2026-08-17 05:57 UTCGHSA enrichment
  22. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.7 · severity → HIGH
  23. 2026-08-17 05:28 UTCEG score recompute
  24. 2026-08-17 05:28 UTCGHSA enrichment
  25. 2026-08-17 05:24 UTCMITRE cvelistV5
Show 6 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 06:23 UTCNVD update
  5. 2026-08-15 06:03 UTCEG score recompute
  6. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72487?
CVE-2026-72487 is a high vulnerability published on August 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:pcigetrom_size+0x52/0x220 Call Trace:…
When was CVE-2026-72487 disclosed?
CVE-2026-72487 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72487 actively exploited?
CVE-2026-72487 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.1% of all scored CVEs.
What is the CVSS score of CVE-2026-72487?
CVE-2026-72487 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-72487?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72487, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72487

Explore →

Is Your Infrastructure Affected by CVE-2026-72487?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs