drm/amdgpu: fix IP instance memory leak on kobject add failure

Overview

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)

Affected

• Linux >= a6c40b178092f41b9d6cc8615697c14b1e5a1c3a < 0563b26c1437fe7e25ea42c334eb85c0a703f8ff
• Linux >= a6c40b178092f41b9d6cc8615697c14b1e5a1c3a < 7ca44cb14d0249992a8f1425ba004d6e2d16d255
• Linux >= a6c40b178092f41b9d6cc8615697c14b1e5a1c3a < c05bbcc263d67b8b158e2a52be7e3005895969d1
• Linux >= a6c40b178092f41b9d6cc8615697c14b1e5a1c3a < f5a5add3605935163dd0f75749b6a7869e9765af
• Linux 5.18

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.