CVE-2026-98779: Linux kernel · drm/amdgpu: fix ACP MFD device leak on init failure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f0013046151b7467e62c471c1c83d63ea255799c : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:07 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f0013046151b7467e62c471c1c83d63ea255799c, d700c26ed64bd3c26e4aa7679b9d5f3333c3747a, abf854513bc19e6e24d45353ac99ec5627ee0acc +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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)
References
- git.kernel.org/stable/c/d700c26ed64bd3c26e4aa7679b9d5f3333c3747a (opens in a new tab)
- git.kernel.org/stable/c/2b9a53940a2bc063ea4cd09ee49220a503a0170c (opens in a new tab)
- git.kernel.org/stable/c/587469076e4ffb617f7ad1a0c4a13072a3e87113 (opens in a new tab)
- git.kernel.org/stable/c/abf854513bc19e6e24d45353ac99ec5627ee0acc (opens in a new tab)
- git.kernel.org/stable/c/f0013046151b7467e62c471c1c83d63ea255799c (opens in a new tab)