drm/amdgpu: fix ACP MFD device leak on init failure
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f0013046151b7467e62c471c1c83d63ea255799c, Kernel 2b9a53940a2bc063ea4cd09ee49220a503a0170c, Kernel 385ad314f1c096aae71fff516214bb312a6047fb and 12 more.
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)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=25030321ba2860c56651429a4f28d94a6483d952 <f0013046151b7467e62c471c1c83d63ea255799c, >=25030321ba2860c56651429a4f28d94a6483d952 <2b9a53940a2bc063ea4cd09ee49220a503a0170c, >=25030321ba2860c56651429a4f28d94a6483d952 <385ad314f1c096aae71fff516214bb312a6047fb, >=25030321ba2860c56651429a4f28d94a6483d952 <587469076e4ffb617f7ad1a0c4a13072a3e87113, >=25030321ba2860c56651429a4f28d94a6483d952 <65ef6645982ccde16a7bc98d025eb80f5fab47f6, >=25030321ba2860c56651429a4f28d94a6483d952 <7b7f770f48be77ce38e93216983dcdf1ea3a42ba, >=25030321ba2860c56651429a4f28d94a6483d952 <abf854513bc19e6e24d45353ac99ec5627ee0acc, >=25030321ba2860c56651429a4f28d94a6483d952 <d700c26ed64bd3c26e4aa7679b9d5f3333c3747a, =4.6 | f0013046151b7467e62c471c1c83d63ea255799c, 2b9a53940a2bc063ea4cd09ee49220a503a0170c, 385ad314f1c096aae71fff516214bb312a6047fb, 587469076e4ffb617f7ad1a0c4a13072a3e87113, 65ef6645982ccde16a7bc98d025eb80f5fab47f6, 7b7f770f48be77ce38e93216983dcdf1ea3a42ba, abf854513bc19e6e24d45353ac99ec5627ee0acc, d700c26ed64bd3c26e4aa7679b9d5f3333c3747a |
| linux-kernel: Kernel | >=5.11.0 <5.15.224, >=5.16.0 <6.1.191, >=6.13.0 <6.18.56, >=6.19.0 <7.2.10, >=6.2.0 <6.6.160, >=6.7.0 <6.12.113, >=4.6.0 <5.10.273 | 5.15.224, 6.1.191, 6.18.56, 7.2.10, 6.6.160, 6.12.113, 5.10.273 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket