CVE-2025-39723: Linux kernel · netfs: Fix unbuffered write error handling
Source GCVE Database
Not known to be exploited · CVSS 7.8 High.
Data as of 19 Nov 2026, 02:21 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Sep 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 18 Nov 2026.
What to do
AI-suggested
A fix for this vulnerability has been implemented in the Linux kernel by correcting the error handling logic in netfs unbuffered writes. Users should apply the official kernel updates that include this fix once available. Until patched, avoid workloads that trigger unbuffered write failures in netfs, such as CIFS with cache=none under low disk space conditions.
Description
CVE-2025-39723 is a high-severity vulnerability in the Linux kernel's netfs subsystem related to unbuffered write error handling. When all subrequests in an unbuffered write stream fail, the system incorrectly returns a large transferred value (LONG_MAX) instead of an error, leading to kernel NULL pointer dereference and potential system crash. The issue was discovered during testing with CIFS and fixed by properly tracking the validity of transferred values and initializing them correctly.
References
- nvd.nist.gov/vuln/detail/CVE-2025-39723 (opens in a new tab)
- git.kernel.org/stable/c/387164a2b97e1f5404c6d0049a7409bac7d2bc5b (opens in a new tab)
- git.kernel.org/stable/c/a3de58b12ce074ec05b8741fa28d62ccb1070468 (opens in a new tab)
- git.kernel.org/stable/c/f08c80af3c9a9849cd178b4843b7c01d103506a1 (opens in a new tab)