Resource leak via missing device-tree node release
Published Dec 30, 2025 · Updated Dec 30, 2025
A reference leak in the Linux kernel beginning with 3.1 allows attackers to retain device-tree node references during AMBA device teardown. The amba_device_release function fails to call of_node_put after device-tree creation increments the node reference count. The public advisory identifies no attacker-controlled trigger or demonstrated service interruption, leaving reachability and operational impact undisclosed.
Summary
What happened
A reference leak in the Linux kernel beginning with 3.1 allows attackers to retain device-tree node references during AMBA device teardown. The amba_device_release function fails to call of_node_put after device-tree creation increments the node reference count. The public advisory identifies no attacker-controlled trigger or demonstrated service interruption, leaving reachability and operational impact undisclosed.
The record
- CVE
- CVE-2023-54230
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 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=3.1
- Affected versionversion=5de1540b7bc4c23470f86add1e517be41e7fefe2 <03db4fe7917bb160eeccf3968835475fa32b7e10
- Affected versionversion=5de1540b7bc4c23470f86add1e517be41e7fefe2 <206fadb7278ceac7593dd0b945a77b9df856a674
- Affected versionversion=5de1540b7bc4c23470f86add1e517be41e7fefe2 <4f1807fddd9bf175ee5e14fffc6b6106e4b297ef
- Affected versionversion=5de1540b7bc4c23470f86add1e517be41e7fefe2 <81ff633a88be2482c163d3acd2801d501261ce6a
- Affected versionversion=5de1540b7bc4c23470f86add1e517be41e7fefe2 <8b60a706166de5de82314494704c2419e7657bf8
- Affected versionversion=5de1540b7bc4c23470f86add1e517be41e7fefe2 <9062ce0ccbd82fbe81cc839a512c0ad90847e01c
- Affected versionversion=5de1540b7bc4c23470f86add1e517be41e7fefe2 <94e398df32e850f26828690ee62f7441979583cc
- Affected versionversion=5de1540b7bc4c23470f86add1e517be41e7fefe2 <9baf2278b3eed2c50112169121257d8a6ee0606c
- Affected versionversion=5de1540b7bc4c23470f86add1e517be41e7fefe2 <e312cbdc11305568554a9e18a2ea5c2492c183f3
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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
No sourced classifications are available.
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