Local availability loss via ibmebus name leak
Published Dec 24, 2025 · Updated Dec 24, 2025
Memory leakage in the Linux kernel's pSeries ibmebus initialization allows local users to reduce availability through a registration failure. When device_register() fails, ibmebus_bus_init() omits put_device(), retaining the kobject name allocated by dev_set_name() instead of freeing it during kobject cleanup. Reachability requires a powerpc pSeries system and a failing ibmebus device registration; the bounded consequence is leaked kernel memory.
Summary
What happened
Memory leakage in the Linux kernel's pSeries ibmebus initialization allows local users to reduce availability through a registration failure. When device_register() fails, ibmebus_bus_init() omits put_device(), retaining the kobject name allocated by dev_set_name() instead of freeing it during kobject cleanup. Reachability requires a powerpc pSeries system and a failing ibmebus device registration; the bounded consequence is leaked kernel memory.
The record
- CVE
- CVE-2023-54017
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3cc4c2f6c266fe5b33a7fa797f31e8b3f06ce58c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7ffe14fce7425c32e735bdc44bce425f18976a49
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <96f27ff732208dce6468016e7a7d5032bd1bfc23
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9f3b2b666833ebef6d0ce5a40e189f38e70342a1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <afda85b963c12947e298ad85d757e333aa40fd74
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d35e7ae10eb8917883da2a0b1823c620a1be42d6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e4ff88548defafb1ef84facd9856ec252da7b008
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ebd8dc974fcc59e2851a0d89ee7935b55142dc8e
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo