CVE-2023-54005
Published Dec 24, 2025
Modified Apr 15, 2026
Description
In the Linux kernel, the following vulnerability has been resolved: binder: fix memory leak in binder_init() In binder_init(), the destruction of binder_alloc_shrinker_init() is not performed in the wrong path, which will cause memory leaks. So this commit introduces binder_alloc_shrinker_exit() and calls it in the wrong path to fix that.
Is your site exposed to CVE-2023-54005?
Run a free security scan — no signup, results in seconds.
References
Other References
https://git.kernel.org/stable/c/03eebad96233397f951d8e9fafd82a1674a77284
https://git.kernel.org/stable/c/486dd742ba186ea333664c517d6775b06b1448ca
https://git.kernel.org/stable/c/adb9743d6a08778b78d62d16b4230346d3508986
https://git.kernel.org/stable/c/b97dad01c12169991f895de3d4f61b8115d12bab
https://git.kernel.org/stable/c/ceb0f8cc987fb3d25c06b9662e08a42f99651207
https://git.kernel.org/stable/c/d7e5e2b87f5d27469075b6326b6b358e38cd9dcb
https://git.kernel.org/stable/c/ee95051c0c1928051f86198bf5e554277a53b26b
https://git.kernel.org/stable/c/f11a26633eb6d3bb24a10b1bacc4e4a9b0c6389f
Frequently Asked Questions
What is CVE-2023-54005? +
In the Linux kernel, the following vulnerability has been resolved:
binder: fix memory leak in binder_init()
In binder_init(), the destruction of binder_alloc_shrinker_init() is not
performed in the wrong path, which will cause memory leaks. So this commit
introduces binder_alloc_shrinker_exit() and calls it in the wrong path to
fix that.
How do I check if I'm vulnerable to CVE-2023-54005? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.