# CVE-2026-98779: drm/amdgpu: fix ACP MFD device leak on init failure

> A memory leak in the AMD GPU driver's ACP initialization failure path can lead to resource exhaustion and 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:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-109334, BELL-CVE-2026-98779, DEBIAN-CVE-2026-98779, GHSA-7q7p-f6vv-qrwf, UBUNTU-CVE-2026-98779

## What is CVE-2026-98779?

CVE-2026-98779 is a memory corruption vulnerability in Linux, published on 18 Oct 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: fix ACP MFD device leak on init failure

acp_hw_init() registers ACP child devices with mfd_add_devices() before
attaching them to the ACP power domain and initializing the hardware.

If attaching a child to the power domain fails, or if the ACP reset or
clock enable operation times out, the failure path frees only the
source cell, resource, and platform-data allocations. The child
platform devices already registered by mfd_add_devices() remain
registered and are never released.

Remove the children from the power domain and unregister the MFD
devices on failures that occur after mfd_add_devices() succeeds. Keep
mfd_add_devices() failures on the existing cleanup path since the MFD
core already rolls back partially registered children itself.

The issue was identified by a static analysis tool I developed and
confirmed by manual review.

(cherry picked from commit 63da68d6a2279ec945581c990c5a59a5ae8b5560)

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


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

Apply the vendor's patch.

## Is CVE-2026-98779 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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