Kernel crash via invalid NFS unlock context
Published Jun 18, 2025 · Updated May 11, 2026
NULL pointer dereference in the Linux kernel NFS client allows local users to crash the kernel during low-memory NFSv4 unlock handling. When nfs_get_lock_context returns -ENOMEM, the unlock path retains the error-valued l_ctx in nfs4_unlockdata and passes it to rpc_run_task, which dereferences a null context in nfs4_locku_prepare. Exploitation requires low-privilege local access, an NFSv4 unlock operation, and allocation failure under memory pressure; the bounded consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in the Linux kernel NFS client allows local users to crash the kernel during low-memory NFSv4 unlock handling. When nfs_get_lock_context returns -ENOMEM, the unlock path retains the error-valued l_ctx in nfs4_unlockdata and passes it to rpc_run_task, which dereferences a null context in nfs4_locku_prepare. Exploitation requires low-privilege local access, an NFSv4 unlock operation, and allocation failure under memory pressure; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2025-38023
- Published
- Jun 18, 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
- Jun 18, 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=4.12
- Affected versionversion=f30cb757f680f965ba8a2e53cb3588052a01aeb5 <4c189fd40a09a03f9a900bedb2d9064f1734d72a
- Affected versionversion=f30cb757f680f965ba8a2e53cb3588052a01aeb5 <72f552e00c50f265896d3c19edc6696aa2910081
- Affected versionversion=f30cb757f680f965ba8a2e53cb3588052a01aeb5 <85fb7f8ca5f8c138579fdfc9b97b3083e6077d40
- Affected versionversion=f30cb757f680f965ba8a2e53cb3588052a01aeb5 <a6879a076b98c99c9fe747816fe1c29543442441
- Affected versionversion=f30cb757f680f965ba8a2e53cb3588052a01aeb5 <c457dc1ec770a22636b473ce5d35614adfe97636
- Affected versionversion=f30cb757f680f965ba8a2e53cb3588052a01aeb5 <da824f1271633bcb515ca8084cda3eda4b3ace51
- Affected versionversion=f30cb757f680f965ba8a2e53cb3588052a01aeb5 <db6f5ee1fc8f54d079d0751292c2fc2d78e3aad1
- Affected versionversion=f30cb757f680f965ba8a2e53cb3588052a01aeb5 <f601960af04d2ecb007c928ba153d34051acd9c1
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