Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98779drm/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)

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 12 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 25030321ba2860c56651429a4f28d94a6483d952 – < 385ad314f1c096aae71fff516214bb312a6047fb
    • affected 25030321ba2860c56651429a4f28d94a6483d952 – < 7b7f770f48be77ce38e93216983dcdf1ea3a42ba
    • affected 25030321ba2860c56651429a4f28d94a6483d952 – < 65ef6645982ccde16a7bc98d025eb80f5fab47f6
    • affected 25030321ba2860c56651429a4f28d94a6483d952 – < d700c26ed64bd3c26e4aa7679b9d5f3333c3747a
    • affected 25030321ba2860c56651429a4f28d94a6483d952 – < 2b9a53940a2bc063ea4cd09ee49220a503a0170c
    • affected 25030321ba2860c56651429a4f28d94a6483d952 – < 587469076e4ffb617f7ad1a0c4a13072a3e87113
    • affected 25030321ba2860c56651429a4f28d94a6483d952 – < abf854513bc19e6e24d45353ac99ec5627ee0acc
    • affected 25030321ba2860c56651429a4f28d94a6483d952 – < f0013046151b7467e62c471c1c83d63ea255799c
  • Linux · Linux

    • affected 4.6
    • unaffected < 4.6
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.56 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98779 badge
[![CVE-2026-98779](https://cveledger.app/badge/CVE-2026-98779.svg)](https://cveledger.app/cve/CVE-2026-98779)

Record last updated .