CVE-2023-54017

powerpc/pseries: fix possible memory leak in ibmebus_bus_init()

N/A

Published: December 24, 2025 at 10:55 AM UTC

Updated: June 17, 2026 at 06:46 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries: fix possible memory leak in ibmebus_bus_init() If device_register() returns error in ibmebus_bus_init(), name of kobject which is allocated in dev_set_name() called in device_add() is leaked. As comment of device_add() says, it should call put_device() to drop the reference count that was set in device_initialize() when it fails, so the name can be freed in kobject_cleanup().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

2.6.16 ≤ v < 4.14.3262.6.16 ≤ v < 4.19.2952.6.16 ≤ v < 5.10.1972.6.16 ≤ v < 5.15.1332.6.16 ≤ v < 5.4.2572.6.16 ≤ v < 6.1.552.6.16 ≤ v < 6.5.52.6.16 ≤ v < 6.62.6.16d7a301033f1990188f65abf4fe8e5b90ef0e3888

Vendor states this is fixed in 3cc4c2f6c266fe5b33a7fa797f31e8b3f06ce58c (fixed)

Vendor states this is fixed in 7ffe14fce7425c32e735bdc44bce425f18976a49 (fixed)

Vendor states this is fixed in 96f27ff732208dce6468016e7a7d5032bd1bfc23 (fixed)

Vendor states this is fixed in 9f3b2b666833ebef6d0ce5a40e189f38e70342a1 (fixed)

Vendor states this is fixed in afda85b963c12947e298ad85d757e333aa40fd74 (fixed)

Vendor states this is fixed in d35e7ae10eb8917883da2a0b1823c620a1be42d6 (fixed)

Vendor states this is fixed in e4ff88548defafb1ef84facd9856ec252da7b008 (fixed)

Vendor states this is fixed in ebd8dc974fcc59e2851a0d89ee7935b55142dc8e (fixed)

Vendor states this is fixed in 2.6.16 (unaffected)

Vendor states this is fixed in 4.14.326 (unaffected)

Vendor states this is fixed in 4.19.295 (unaffected)

Vendor states this is fixed in 5.10.197 (unaffected)