Live › vulnerability › CVE-2026-98780
Go to dashboardIn the Linux kernel's amdgpu graphics driver, a failed kobject_add() during IP discovery sysfs setup skips releasing the object, leaking a small kernel allocation. The sources describe a memory leak with no stated attacker capability.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the amdgpu driver loaded, typically machines with AMD Radeon or APU graphics. The leak only occurs when sysfs registration of an IP instance fails, which the sources do not describe as common. Systems without amdgpu hardware can skip it.
No product ranges from the sources yet.
uname -r and check whether the kernel includes the amdgpu driver (lsmod | grep amdgpu)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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)
This page as .md · .json · in your agent: get_signal("CVE-2026-98780")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.