drm/amdgpu: fix ACP MFD device leak on init failure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.113, 6.18.56, 7.2.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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)
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 25030321ba2860c56651429a4f28d94a6483d952 · fixed in d700c26ed64bd3c26e4aa7679b9d5f3333c3747a; From 25030321ba2860c56651429a4f28d94a6483d952 · fixed in 2b9a53940a2bc063ea4cd09ee49220a503a0170c; From 25030321ba2860c56651429a4f28d94a6483d952 · fixed in 587469076e4ffb617f7ad1a0c4a13072a3e87113; From 25030321ba2860c56651429a4f28d94a6483d952 · fixed in abf854513bc19e6e24d45353ac99ec5627ee0acc; From 25030321ba2860c56651429a4f28d94a6483d952 · fixed in f0013046151b7467e62c471c1c83d63ea255799c
- Linux Linux
4.6
- KernelLinux
From 4.6.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10