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)
Published: 2026-10-18
Score: 1.9 Low
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service via Resource Exhaustion
Action: Patch
AI Analysis

Impact

The defect occurs when the amdgpu ACP driver registers child devices with the multi‑device framework before successfully attaching them to the power domain. If the attach fails or if a reset/clock enable operation times out, only the source cell, resource, and platform‑data allocations are freed; the child platform devices remain registered. This leads to a resource leak that can accumulate over time, eventually exhausting kernel resources and destabilizing the system. The weakness is an improper resource release (CWE‑772).

Affected Systems

Linux kernel builds that include the amdgpu DRM driver and its ACP power‑domain integration are affected. The vulnerability applies to any kernel prior to the patch from commit 63da68d6a2279ec945581c990c5a59a5ae8b5560, regardless of architecture but only when the amdgpu module is loaded.

Risk and Exploitability

The flaw is local; the attacker must be able to trigger the adverse initialization path, which is inferred that requires root or the ability to induce a power‑domain failure. The CVSS score is 1.9, indicating a low severity. The EPSS score is <1% and the vulnerability is not listed in CISA's KEV catalog. Consequently, the overall risk is limited to affected kernels and to contexts where the attacker can provoke the initialization failure, but the potential for resource exhaustion makes it a serious local denial‑of‑service issue.

Generated by OpenCVE AI on October 23, 2026 at 19:43 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the kernel to a build that includes the change from commit 63da68d6a2279ec945581c990c5a59a5ae8b5560.
  • If an upgrade is not possible, unload or disable the amdgpu module to avoid the vulnerable initialization path.
  • Monitor kernel logs for repeated ACP initialization failures and abnormal MFD device registration counts to detect potential leaks.

Generated by OpenCVE AI on October 23, 2026 at 19:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4850-1 linux-6.12 security update
History

Fri, 30 Oct 2026 13:00:00 +0000


Fri, 23 Oct 2026 18:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-400

Fri, 23 Oct 2026 12:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-772
References
Metrics threat_severity

None

cvssV3_1

{'score': 1.9, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L'}

threat_severity

Low


Wed, 21 Oct 2026 13:15:00 +0000


Sun, 18 Oct 2026 23:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-400

Sun, 18 Oct 2026 16:00:00 +0000

Type Values Removed Values Added
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)
Title drm/amdgpu: fix ACP MFD device leak on init failure
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-30T12:39:46.267Z

Reserved: 2026-09-25T10:25:14.369Z

Link: CVE-2026-98779

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-18T16:17:31.853

Modified: 2026-10-30T13:21:27.513

Link: CVE-2026-98779

cve-icon Redhat

Severity : Low

Publid Date: 2026-10-18T00:00:00Z

Links: CVE-2026-98779 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-23T19:45:17Z

Weaknesses
  • CWE-772

    Missing Release of Resource after Effective Lifetime