Local kernel crash via NULL lockspace dereference
Published Apr 16, 2025 · Updated Jul 4, 2026
NULL pointer dereference in the DLM subsystem in Linux 2.6.31 through 6.14.1 allows local users to crash the kernel via event_done. The lockspace creation path treats a positive do_uevent return as success after clearing the lockspace pointer, and device_create_lockspace passes that NULL pointer to dlm_find_lockspace_local. A local user able to write a positive value to the DLM event_done attribute can trigger the crash; confidentiality and integrity are unaffected.
Summary
What happened
NULL pointer dereference in the DLM subsystem in Linux 2.6.31 through 6.14.1 allows local users to crash the kernel via event_done. The lockspace creation path treats a positive do_uevent return as success after clearing the lockspace pointer, and device_create_lockspace passes that NULL pointer to dlm_find_lockspace_local. A local user able to write a positive value to the DLM event_done attribute can trigger the crash; confidentiality and integrity are unaffected.
The record
- CVE
- CVE-2025-23131
- Published
- Apr 16, 2025
- Updated
- Jul 4, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 2025CVE publishedPublication date reported by the CVE source.
- Jul 4, 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=2.6.31
- Affected versionversion=8511a2728ab82cab398e39d019f5cf1246021c1c <10b7a59814765d18d43555c9cef4eb3048b7e8a3
- Affected versionversion=8511a2728ab82cab398e39d019f5cf1246021c1c <7109d69bec6edce546dc870e66bd2b668a3d5549
- Affected versionversion=8511a2728ab82cab398e39d019f5cf1246021c1c <8e2bad543eca5c25cd02cbc63d72557934d45f13
- Affected versionversion=8511a2728ab82cab398e39d019f5cf1246021c1c <a1c41aebb184d9228a440dcb6761224e65b0e49a
- Affected versionversion=8511a2728ab82cab398e39d019f5cf1246021c1c <b73c4ad4d387fe5bc988145bd9f1bc0de76afd5c
- Affected versionversion=8511a2728ab82cab398e39d019f5cf1246021c1c <c7837e2c96559663c33f43da403d9cf3cf77cfa7
- Affected versionversion=8511a2728ab82cab398e39d019f5cf1246021c1c <ee28d99d789b077565cbe0377374d1e826c64d93
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