Skip to main content
VulnerabilityPublished Updated

CVE-2026-98780: Linux kernel · drm/amdgpu: fix IP instance memory leak on kobject add failure

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f6364e7284a131556f5d763d867147bece2843a8 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:07 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f6364e7284a131556f5d763d867147bece2843a8, f5a5add3605935163dd0f75749b6a7869e9765af, c05bbcc263d67b8b158e2a52be7e3005895969d1 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a6c40b178092f41b9d6cc8615697c14b1e5a1c3a, < f6364e7284a131556f5d763d867147bece2843a8
Fixed in
  • f6364e7284a131556f5d763d867147bece2843a8
LinuxLinuxAffected
  • ≥ a6c40b178092f41b9d6cc8615697c14b1e5a1c3a, < f5a5add3605935163dd0f75749b6a7869e9765af
Fixed in
  • f5a5add3605935163dd0f75749b6a7869e9765af
LinuxLinuxAffected
  • ≥ a6c40b178092f41b9d6cc8615697c14b1e5a1c3a, < c05bbcc263d67b8b158e2a52be7e3005895969d1
Fixed in
  • c05bbcc263d67b8b158e2a52be7e3005895969d1
LinuxLinuxAffected
  • ≥ a6c40b178092f41b9d6cc8615697c14b1e5a1c3a, < 0563b26c1437fe7e25ea42c334eb85c0a703f8ff
Fixed in
  • 0563b26c1437fe7e25ea42c334eb85c0a703f8ff
LinuxLinuxAffected
  • ≥ a6c40b178092f41b9d6cc8615697c14b1e5a1c3a, < 7ca44cb14d0249992a8f1425ba004d6e2d16d255
Fixed in
  • 7ca44cb14d0249992a8f1425ba004d6e2d16d255
LinuxLinuxAffected
  • =5.18
Fixed in–

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)

References

Community reviews

Loading reviews…