# CVE-2026-80747: drm/amdkfd: Add bounds check for CRAT subtype length

> A missing bounds check in the Linux kernel's AMD KFD driver allows out-of-bounds reads via malformed CRAT tables, potentially causing information disclosure or crashes.

- **Severity:** High 8.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-99041, BELL-CVE-2026-80747, DEBIAN-CVE-2026-80747, GHSA-9jrx-pr9x-qp88, UBUNTU-CVE-2026-80747

## What is CVE-2026-80747?

CVE-2026-80747 is a high-severity memory corruption vulnerability in Linux, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/amdkfd: Add bounds check for CRAT subtype length

The CRAT parser validates that the subtype header fits within the image,
but does not verify that the advertised subtype length fits. A malformed
CRAT table with an oversized length field causes out-of-bounds reads when
kfd_parse_subtype() casts the header to specific subtype structures.

Add validation that sub_type_hdr + length does not exceed the image
boundary before parsing the subtype contents.

(cherry picked from commit 48e1d1e6e8798aef0312e68d8e586021b5b3cf4d)

## Which versions are affected by CVE-2026-80747?


## How do I fix CVE-2026-80747?

Apply the vendor's patch.

## Is CVE-2026-80747 being exploited?

There is no known exploitation of CVE-2026-80747 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80747 and fix it if it is affected.

What it is: CVE-2026-80747 is a high-severity memory corruption vulnerability in Linux, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80747 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80747/ (Markdown: https://insights.sbomify.com/CVE-2026-80747/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80747
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80747
- OSV: https://osv.dev/vulnerability/CVE-2026-80747

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80747/
Summaries are generated and may contain mistakes; the official description above is the record.