Kernel memory leak via Binder cleanup omission
Published Dec 24, 2025 · Updated Dec 24, 2025
Memory leak in the Linux kernel Binder initialization path from 4.14 allows attackers to retain kernel memory after initialization fails. binder_init registers the global Binder allocation shrinker, but later failure branches return without unregistering it; the missing teardown leaves the shrinker allocation behind. The public record identifies no attacker-controlled method for reaching that error path, so practical reachability and the amount of retained memory are unspecified.
Summary
What happened
Memory leak in the Linux kernel Binder initialization path from 4.14 allows attackers to retain kernel memory after initialization fails. binder_init registers the global Binder allocation shrinker, but later failure branches return without unregistering it; the missing teardown leaves the shrinker allocation behind. The public record identifies no attacker-controlled method for reaching that error path, so practical reachability and the amount of retained memory are unspecified.
The record
- CVE
- CVE-2023-54005
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
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=4.14
- Affected versionversion=f2517eb76f1f2f7f89761f9db2b202e89931738c <03eebad96233397f951d8e9fafd82a1674a77284
- Affected versionversion=f2517eb76f1f2f7f89761f9db2b202e89931738c <486dd742ba186ea333664c517d6775b06b1448ca
- Affected versionversion=f2517eb76f1f2f7f89761f9db2b202e89931738c <adb9743d6a08778b78d62d16b4230346d3508986
- Affected versionversion=f2517eb76f1f2f7f89761f9db2b202e89931738c <b97dad01c12169991f895de3d4f61b8115d12bab
- Affected versionversion=f2517eb76f1f2f7f89761f9db2b202e89931738c <ceb0f8cc987fb3d25c06b9662e08a42f99651207
- Affected versionversion=f2517eb76f1f2f7f89761f9db2b202e89931738c <d7e5e2b87f5d27469075b6326b6b358e38cd9dcb
- Affected versionversion=f2517eb76f1f2f7f89761f9db2b202e89931738c <ee95051c0c1928051f86198bf5e554277a53b26b
- Affected versionversion=f2517eb76f1f2f7f89761f9db2b202e89931738c <f11a26633eb6d3bb24a10b1bacc4e4a9b0c6389f
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