CVE-2026-98779

UnknownEPSS 0.17%

Last modified

CVE-2026-98779 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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)

Metrics

EPSS Probability
0.17%

6.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 25030321ba2860c56651429a4f28d94a6483d952, < 385ad314f1c096aae71fff516214bb312a6047fb; >= 25030321ba2860c56651429a4f28d94a6483d952, < 7b7f770f48be77ce38e93216983dcdf1ea3a42ba; >= 25030321ba2860c56651429a4f28d94a6483d952, < 65ef6645982ccde16a7bc98d025eb80f5fab47f6; >= 25030321ba2860c56651429a4f28d94a6483d952, < d700c26ed64bd3c26e4aa7679b9d5f3333c3747a; >= 25030321ba2860c56651429a4f28d94a6483d952, < 2b9a53940a2bc063ea4cd09ee49220a503a0170c; >= 25030321ba2860c56651429a4f28d94a6483d952, < 587469076e4ffb617f7ad1a0c4a13072a3e87113; >= 25030321ba2860c56651429a4f28d94a6483d952, < abf854513bc19e6e24d45353ac99ec5627ee0acc; >= 25030321ba2860c56651429a4f28d94a6483d952, < f0013046151b7467e62c471c1c83d63ea255799c
LinuxLinux4.6

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98779?
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)
How severe is CVE-2026-98779?
Severity scoring for CVE-2026-98779 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-98779?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-98779?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST