CVE-2025-38023: nfs: handle failure of nfs_get_lock_context in unlock path
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 4c189fd40a09a03f9a900bedb2d9064f1734d72a, 72f552e00c50f265896d3c19edc6696aa2910081, 85fb7f8ca5f8c138579fdfc9b97b3083e6077d40.
Low priority for now. Upgrade to Linux Linux 4c189fd40a09a03f9a900bedb2d9064f1734d72a, 72f552e00c50f265896d3c19edc6696aa2910081, 85fb7f8ca5f8c138579fdfc9b97b3083e6077d40 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: nfs: handle failure of nfs_get_lock_context in unlock path When memory is insufficient, the allocation of nfs_lock_context in nfs_get_lock_context() fails and returns -ENOMEM. If we mistakenly treat an nfs4_unlockdata structure (whose l_ctx member has been set to -ENOMEM) as valid and proceed to execute rpc_run_task(), this will trigger a NULL pointer dereference in nfs4_locku_prepare. For example: BUG: kernel NULL pointer dereference, address: 000000000000000c PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP PTI CPU: 15 UID: 0 PID: 12 Comm: kworker/u64:0 Not tainted 6.15.0-rc2-dirty #60 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 Workqueue: rpciod rpc_async_schedule RIP: 0010:nfs4_locku_prepare+0x35/0xc2 Code: 89 f2 48 89 fd 48 c7 c7 68 69 ef b5 53 48 8b 8e 90 00 00 00 48 89 f3 RSP: 0018:ffffbbafc006bdb8 EFLAGS: 00010246 RAX: 000000000000004b RBX: ffff9b964fc1fa00 RCX: 0000000000000000 RDX: 0000000000000000 RSI: fffffffffffffff4 RDI: ffff9ba53fddbf40 RBP: ffff9ba539934000 R08: 0000000000000000 R09: ffffbbafc006bc38 R10: ffffffffb6b689c8 R11: 0000000000000003 R12: ffff9ba539934030 R13: 0000000000000001 R14: 0000000004248060 R15: ffffffffb56d1c30 FS: 0000000000000000(0000) GS:ffff9ba5881f0000(0000) knlGS:00000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000000000000c CR3: 000000093f244000 CR4: 00000000000006f0 Call Trace: <TASK> __rpc_execute+0xbc/0x480 rpc_async_schedule+0x2f/0x40 process_one_work+0x232/0x5d0 worker_thread+0x1da/0x3d0 ? __pfx_worker_thread+0x10/0x10 kthread+0x10d/0x240 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x34/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Modules linked in: CR2: 000000000000000c ---[ end trace 0000000000000000 ]--- Free the allocated nfs4_unlockdata when nfs_get_lock_context() fails and return NULL to terminate subsequent rpc_run_task, preventing NULL pointer dereference.
- Published
- Jun 18, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-476
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.12affected
- f30cb757f680f965ba8a2e53cb3588052a01aeb5 and later · before db6f5ee1fc8f54d079d0751292c2fc2d78e3aad1affected · git
- f30cb757f680f965ba8a2e53cb3588052a01aeb5 and later · before 4c189fd40a09a03f9a900bedb2d9064f1734d72aaffected · git
- f30cb757f680f965ba8a2e53cb3588052a01aeb5 and later · before 72f552e00c50f265896d3c19edc6696aa2910081affected · git
- f30cb757f680f965ba8a2e53cb3588052a01aeb5 and later · before 85fb7f8ca5f8c138579fdfc9b97b3083e6077d40affected · git
- f30cb757f680f965ba8a2e53cb3588052a01aeb5 and later · before a6879a076b98c99c9fe747816fe1c29543442441affected · git
- f30cb757f680f965ba8a2e53cb3588052a01aeb5 and later · before da824f1271633bcb515ca8084cda3eda4b3ace51affected · git
- f30cb757f680f965ba8a2e53cb3588052a01aeb5 and later · before f601960af04d2ecb007c928ba153d34051acd9c1affected · git
- f30cb757f680f965ba8a2e53cb3588052a01aeb5 and later · before c457dc1ec770a22636b473ce5d35614adfe97636affected · git
- before 4.12not affected · semver
Affected versions · NVD (9)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.5 and later · before 5.10.238
- linux linux kernel5.11 and later · before 5.15.184
- linux linux kernel5.16 and later · before 6.1.140
- linux linux kernel4.12 and later · before 5.4.294
- linux linux kernel6.7 and later · before 6.12.30
- linux linux kernel6.13 and later · before 6.14.8
- linux linux kernel6.2 and later · before 6.6.92
- linux linux kernel6.15
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.140-1 | 6.1.140-1 |
| Debian:13 | linux | before 6.12.30-1 | 6.12.30-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38015Jun 18, 2025 · dmaengine: idxd: fix memory leak in error handling path of idxd_alloc22Monitor
- ← EarlierCVE-2025-38020Jun 18, 2025 · net/mlx5e: Disable MACsec offload for uplink representor profile22Monitor
- Later →CVE-2025-38029Jun 18, 2025 · kasan: avoid sleepable page allocation from atomic context22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4c189fd40a09a03f9a900bedb2d9064f1734d72a | Vendor (CNA) |
| Linux Linux | 72f552e00c50f265896d3c19edc6696aa2910081 | Vendor (CNA) |
| Linux Linux | 85fb7f8ca5f8c138579fdfc9b97b3083e6077d40 | Vendor (CNA) |
| Linux Linux | a6879a076b98c99c9fe747816fe1c29543442441 | Vendor (CNA) |
| Linux Linux | c457dc1ec770a22636b473ce5d35614adfe97636 | Vendor (CNA) |
| Linux Linux | da824f1271633bcb515ca8084cda3eda4b3ace51 | Vendor (CNA) |
| Linux Linux | db6f5ee1fc8f54d079d0751292c2fc2d78e3aad1 | Vendor (CNA) |
| Linux Linux | f601960af04d2ecb007c928ba153d34051acd9c1 | Vendor (CNA) |
| debian:linux | 6.1.140-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/72f552e00c50f265896d3c19edc6696aa2910081
- git.kernel.org/stable/c/85fb7f8ca5f8c138579fdfc9b97b3083e6077d40
- git.kernel.org/stable/c/a6879a076b98c99c9fe747816fe1c29543442441
- git.kernel.org/stable/c/c457dc1ec770a22636b473ce5d35614adfe97636
- git.kernel.org/stable/c/da824f1271633bcb515ca8084cda3eda4b3ace51
- git.kernel.org/stable/c/db6f5ee1fc8f54d079d0751292c2fc2d78e3aad1
- git.kernel.org/stable/c/f601960af04d2ecb007c928ba153d34051acd9c1
- lists.debian.org/debian-lts-announce/2025/08/msg00010.html
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.