Skip to content
Systems

CVE-2026-80747

8.0
High
EPSS 0.16%Patch availableSep 4, 2026

Linux kernel amdkfd CRAT parser OOB read can leak memory or crash.

common questions

Is CVE-2026-80747 being exploited?

Not confirmed. CVE-2026-80747 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.16% probability of exploitation in the next 30 days.

How severe is CVE-2026-80747?

CVE-2026-80747 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-80747?

Yes. A fix has been recorded for CVE-2026-80747. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-80747 affect?

CVE-2026-80747 affects Linux kernel (drm/amdkfd), AMD GPU systems with KFD, Distributions shipping affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-80747?

Apply vendor/distribution kernel updates to the patched stable release.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (drm/amdkfd)AMD GPU systems with KFDDistributions shipping affected kernels
impact

Out-of-bounds read in kernel CRAT parser may disclose kernel memory or trigger kernel crash (DoS) via crafted CRAT/firmware.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 5b5c4e40a37e858e2bff8cd91be8e972256392c4 and < ca91e0cc8087568e4b791648a7c01e804f48cb73
  • affected>= 5b5c4e40a37e858e2bff8cd91be8e972256392c4 and < 6e7566ba4739dd573c331adde1c96690f7a567bd
  • affected3.19
vendor says fixed in< 3.19, >= 7.1.10 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free