Local kernel crash via unchecked percpu allocation
Published May 2, 2025 · Updated May 11, 2026
NULL pointer dereference in Linux device-mapper statistics allows local users to crash the kernel through a failed percpu allocation. dm_stats_init() fails to check whether alloc_percpu() returns NULL, and alloc_dev() continues until dm_stats_cleanup() dereferences the failed allocation. Exploitation requires low-privileged local access and an allocation failure; the reported consequence is a kernel crash without data disclosure or modification.
Summary
What happened
NULL pointer dereference in Linux device-mapper statistics allows local users to crash the kernel through a failed percpu allocation. dm_stats_init() fails to check whether alloc_percpu() returns NULL, and alloc_dev() continues until dm_stats_cleanup() dereferences the failed allocation. Exploitation requires low-privileged local access and an allocation failure; the reported consequence is a kernel crash without data disclosure or modification.
The record
- CVE
- CVE-2023-53044
- Published
- May 2, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 2, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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.12
- Affected versionversion=fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <0d96bd507ed7e7d565b6d53ebd3874686f123b2e
- Affected versionversion=fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <2287d7b721471a3d58bcd829250336e3cdf1635e
- Affected versionversion=fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <443c9d522397511a4328dc2ec3c9c63c73049756
- Affected versionversion=fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <4a32a9a818a895671bd43e0c40351e60e4e9140b
- Affected versionversion=fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <5b66e36a3efd24041b7374432bfa4dec2ff01e95
- Affected versionversion=fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <a42180dd361584816bfe15c137b665699b994d90
- Affected versionversion=fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <c68f08cc745675a17894e1b4a5b5b9700ace6da4
- Affected versionversion=fd2ed4d252701d3bbed4cd3e3d267ad469bb832a <d3aa3e060c4a80827eb801fc448debc9daa7c46b
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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