CVE-2026-98779

drm/amdgpu: fix ACP MFD device leak on init failure

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)

Key facts

Published
18 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.177% likely to be exploited in the next 30 days, higher than 7.352% of CVEs (scores for 18 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 25030321ba2860c56651429a4f28d94a6483d952 up to but excluding 385ad314f1c096aae71fff516214bb312a6047fb (affected)
  • 25030321ba2860c56651429a4f28d94a6483d952 up to but excluding 7b7f770f48be77ce38e93216983dcdf1ea3a42ba (affected)
  • 25030321ba2860c56651429a4f28d94a6483d952 up to but excluding 65ef6645982ccde16a7bc98d025eb80f5fab47f6 (affected)
  • 25030321ba2860c56651429a4f28d94a6483d952 up to but excluding d700c26ed64bd3c26e4aa7679b9d5f3333c3747a (affected)
  • 25030321ba2860c56651429a4f28d94a6483d952 up to but excluding 2b9a53940a2bc063ea4cd09ee49220a503a0170c (affected)
  • 25030321ba2860c56651429a4f28d94a6483d952 up to but excluding 587469076e4ffb617f7ad1a0c4a13072a3e87113 (affected)
  • 25030321ba2860c56651429a4f28d94a6483d952 up to but excluding abf854513bc19e6e24d45353ac99ec5627ee0acc (affected)
  • 25030321ba2860c56651429a4f28d94a6483d952 up to but excluding f0013046151b7467e62c471c1c83d63ea255799c (affected)
LinuxLinux
  • Default status: affected
  • 4.6 (affected)
  • 0 up to but excluding 4.6 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.56 up to and including 6.18.* (unaffected)
  • 7.2.10 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References