CVE-2026-98780: Linux kernel · drm/amdgpu: fix IP instance memory leak on kobject add failure
Source GCVE Database
Not known to be exploited · fixed in f6364e7284a131556f5d763d867147bece2843a8 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
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
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been applied in the Linux kernel to call kobject_put() when kobject_add() fails, preventing the memory leak. Users should update to a kernel version that includes this patch. Since this is a kernel-level fix, applying the official kernel update from the vendor or distribution is the recommended remediation. No additional mitigation steps are indicated.
Description
A memory leak vulnerability in the Linux kernel's amdgpu driver was fixed. The issue occurs when kobject_add() fails during the initialization of ip_hw_instance, causing the allocated memory not to be freed. This happens because the failure return value is ignored and the initial kobject reference is not dropped, preventing normal cleanup. The fix involves calling kobject_put() on failure to properly release the allocation and avoid the leak.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98780 (opens in a new tab)
- git.kernel.org/stable/c/0563b26c1437fe7e25ea42c334eb85c0a703f8ff (opens in a new tab)
- git.kernel.org/stable/c/7ca44cb14d0249992a8f1425ba004d6e2d16d255 (opens in a new tab)
- git.kernel.org/stable/c/c05bbcc263d67b8b158e2a52be7e3005895969d1 (opens in a new tab)
- git.kernel.org/stable/c/f5a5add3605935163dd0f75749b6a7869e9765af (opens in a new tab)
- git.kernel.org/stable/c/f6364e7284a131556f5d763d867147bece2843a8 (opens in a new tab)