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-98780drm/amdgpu: fix IP instance memory leak on kobject add failure

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix IP instance memory leak on kobject add failure amdgpu_discovery_sysfs_ips() allocates ip_hw_instance with kzalloc_flex() and initializes its embedded kobject before calling kobject_add(). If kobject_add() fails, the return value is ignored and execution continues without dropping the initial kobject reference. The failed kobject is not retained in the kset list, so the normal sysfs teardown path cannot find it. As a result, ip_hw_instance_release() is never called and the ip_hw_instance allocation is leaked. Call kobject_put() when kobject_add() fails so the initial reference is dropped and ip_hw_instance_release() can free the allocation. Keep the existing best-effort sysfs behavior by continuing with the remaining IP entries after the failed registration. The issue was identified by a static analysis tool I developed and confirmed by manual review. (cherry picked from commit 5c75fbcca8af1096d8d9415b91d8ea6212c22ee1)

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.19% · top 92% 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 a6c40b178092f41b9d6cc8615697c14b1e5a1c3a – < 1d7dd4f230867231abfc5cc413dae5260e06fdb2
    • affected a6c40b178092f41b9d6cc8615697c14b1e5a1c3a – < f6364e7284a131556f5d763d867147bece2843a8
    • affected a6c40b178092f41b9d6cc8615697c14b1e5a1c3a – < 0563b26c1437fe7e25ea42c334eb85c0a703f8ff
    • affected a6c40b178092f41b9d6cc8615697c14b1e5a1c3a – < 7ca44cb14d0249992a8f1425ba004d6e2d16d255
    • affected a6c40b178092f41b9d6cc8615697c14b1e5a1c3a – < c05bbcc263d67b8b158e2a52be7e3005895969d1
    • affected a6c40b178092f41b9d6cc8615697c14b1e5a1c3a – < f5a5add3605935163dd0f75749b6a7869e9765af
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • 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

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .