VulnerabilityPublished 4 Jul 2025Updated 5 Nov 2026

CVE-2025-38231: Linux kernel · nfsd: Initialize ssc before laundromat_work to prevent NULL dereference

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in deaeb74ae9318252829c59a84a7d2316fc335660 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:04 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch

Available – fixed in deaeb74ae9318252829c59a84a7d2316fc335660, d622c2ee6c08147ab8c9b9e37d93b6e95d3258e0, b31da62889e6d610114d81dc7a6edbcaa503fcf8 +5

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=5.10.220 <5.10.239	Fixed in deaeb74ae9318252829c59a84a7d2316fc335660 d622c2ee6c08147ab8c9b9e37d93b6e95d3258e0 b31da62889e6d610114d81dc7a6edbcaa503fcf8 a97668ec6d73dab237cd1c15efe012a10090a4ed 5060e1a5fef184bd11d298e3f0ee920d96a23236 83ac1ba8ca102ab5c0ed4351f8ac6e74ac4d5d64 5.10.239 0fccf5f01ed28725cc313a66ca1247eef911d55e
LinuxLinux	Affected =5.14	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: Initialize ssc before laundromat_work to prevent NULL dereference In nfs4_state_start_net(), laundromat_work may access nfsd_ssc through nfs4_laundromat -> nfsd4_ssc_expire_umount. If nfsd_ssc isn't initialized, this can cause NULL pointer dereference. Normally the delayed start of laundromat_work allows sufficient time for nfsd_ssc initialization to complete. However, when the kernel waits too long for userspace responses (e.g. in nfs4_state_start_net -> nfsd4_end_grace -> nfsd4_record_grace_done -> nfsd4_cld_grace_done -> cld_pipe_upcall -> __cld_pipe_upcall -> wait_for_completion path), the delayed work may start before nfsd_ssc initialization finishes. Fix this by moving nfsd_ssc initialization before starting laundromat_work.

References

Community reviews

Loading reviews…