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)
Published: 2026-10-18
Score: 1.9 Low
EPSS: < 1% Very Low
KEV: No
Impact: Memory Leak potentially leading to Resource Exhaustion
Action: Apply Patch
AI Analysis

Impact

The amdgpu driver allocates an IP hardware instance and embeds a kobject during device initialization. If the kobject_add() call fails, the error is ignored and the initial reference is left unreleased. As a result, the ip_hw_instance_release() routine is never invoked and the memory allocated for the instance leaks into the kernel's data segment.

Affected Systems

The vulnerability affects the amdgpu graphics driver within the Linux kernel. No specific kernel release or version range is listed, so versions containing the unpatched amdgpu code prior to the described commit may be impacted.

Risk and Exploitability

This is a local kernel error; there is no known external trigger to force the failure path. The CVSS score is 1.9 and the EPSS score is < 1%, and the vulnerability is not listed in the CISA KEV catalog, so the likelihood of exploitation in the wild is uncertain. The risk arises from the accumulation of leaked memory over time, potentially exhausting system resources and degrading kernel stability or availability.

Generated by OpenCVE AI on October 23, 2026 at 19:43 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a release that includes the amdgpu kobject memory‑leak fix.
  • If an upgrade is not feasible, disable the AMDGPU driver or reduce GPU activity to limit the creation of IP instances until the patch can be applied.
  • Coordinate with system administrators to apply the official kernel update as soon as it is released.

Generated by OpenCVE AI on October 23, 2026 at 19:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4850-1 linux-6.12 security update
History

Fri, 30 Oct 2026 13:00:00 +0000


Fri, 23 Oct 2026 18:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-401

Fri, 23 Oct 2026 12:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-772
References
Metrics threat_severity

None

cvssV3_1

{'score': 1.9, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L'}

threat_severity

Low


Wed, 21 Oct 2026 13:15:00 +0000


Sun, 18 Oct 2026 22:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-401

Sun, 18 Oct 2026 16:00:00 +0000

Type Values Removed Values Added
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)
Title drm/amdgpu: fix IP instance memory leak on kobject add failure
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-30T12:39:47.351Z

Reserved: 2026-09-25T10:25:14.369Z

Link: CVE-2026-98780

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-18T16:17:31.960

Modified: 2026-10-30T13:21:27.643

Link: CVE-2026-98780

cve-icon Redhat

Severity : Low

Publid Date: 2026-10-18T00:00:00Z

Links: CVE-2026-98780 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-23T19:45:17Z

Weaknesses
  • CWE-772

    Missing Release of Resource after Effective Lifetime