# CVE-2026-68238: drm/amdgpu: Release VFCT ACPI table reference

> A memory leak in the Linux kernel amdgpu driver allows local attackers to exhaust system resources, causing denial of service.

- **Severity:** Not scored
- **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:** 10 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-95235, BELL-CVE-2026-68238, DEBIAN-CVE-2026-68238, GHSA-cp54-xgp7-w9qr, UBUNTU-CVE-2026-68238

## What is CVE-2026-68238?

CVE-2026-68238 is a memory corruption vulnerability in Linux, published on 10 Aug 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/amdgpu: Release VFCT ACPI table reference

amdgpu_acpi_vfct_bios() fetches the VFCT table with acpi_get_table()
but never releases it. acpi_get_table() takes a reference on the
table (incrementing its validation_count and mapping it on the 0->1
transition); without a paired acpi_put_table() the mapping is leaked
on every call, whether or not a matching VBIOS image is found.

Route all exit paths after the table is acquired through a common
acpi_put_table(). The VBIOS image is copied out with kmemdup() before
the table is released, so it remains valid for the caller.

(cherry picked from commit ca5988682b4cba4cd125a0fa99b2de1239164ae4)

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


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

Apply the vendor's patch.

## Is CVE-2026-68238 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68238 is a memory corruption vulnerability in Linux, published on 10 Aug 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-68238 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-68238/ (Markdown: https://insights.sbomify.com/CVE-2026-68238/index.md)
```

## Sources

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

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