An integer overflow when calculating physical offsets for sparse PMRs may result in 32-bit truncation of address computations for PMRs larger than 4 GB. This can lead to incorrect GPU MMU mappings and may allow a non-privileged user to trigger access to unintended physical memory, resulting in memory corruption or information disclosure.
CVE-2026-16280
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-25. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 59(Track)EG Risk 59/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 computedSeverity98% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
July 24, 2026
Last Modified
July 28, 2026
Advisory Details (1)
Auto-updated Jul 28, 2026Imagination GPU Driver Vulnerabilities - Imagination
https://www.imaginationtech.com/gpu-driver-vulnerabilities/Vendor Advisories for CVE-2026-16280(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 21× 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.
- 2026-07-28 16:31 UTCEG score recompute
- 2026-07-28 16:31 UTCGHSA enrichment
- 2026-07-28 14:31 UTCGHSA enrichment
- 2026-07-28 10:04 UTCGHSA enrichment
- 2026-07-28 05:39 UTCGHSA enrichment
- 2026-07-28 01:14 UTCGHSA enrichment
- 2026-07-27 20:49 UTCEG score recompute
- 2026-07-27 20:49 UTCGHSA enrichment
- 2026-07-27 16:17 UTCEG score recompute▲ 9.80
- 2026-07-27 16:17 UTCGHSA enrichment
- 2026-07-27 16:16 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 02:55 UTCEG score recompute
- 2026-07-26 02:54 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 00:11 UTCNVD update
- 2026-07-24 22:28 UTCEG score recompute
- 2026-07-24 22:26 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-190
Frequently asked(5)
What is CVE-2026-16280?
When was CVE-2026-16280 disclosed?
Is CVE-2026-16280 actively exploited?
What is the CVSS score of CVE-2026-16280?
How do I remediate CVE-2026-16280?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16280
Is Your Infrastructure Affected by CVE-2026-16280?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.