All vulnerabilities

Servers and applications

CVE-2026-99375

NFSv4/flexfiles: fail I/O to the data server once a lock is lost

Severity
Unrated
Published
19 Nov 2026
Last changed
19 Nov 2026
Added to UpHeron
19 Nov 2026
Fixed in
6.12.117, 6.18.61, 7.3.2
Sources
CVE Program

Description

In the Linux kernel, the following vulnerability has been resolved:

When a client loses a byte-range lock, because its lease expired and it may not recover the lock (nfs.recover_lost_locks=0) or because reclaim failed, it marks the lock state NFS_LOCK_LOST and fails further I/O by that lock owner. Otherwise an application that believes it holds a lock over a range is never told that the lock is gone, and can overwrite data that another client has since written under its own lock on that range.

The NFSv4 READ/WRITE and file layout I/O paths apply this in rpc_call_prepare, where nfs4_set_rw_stateid() returns -EIO for a lost lock. The flexfiles data server I/O path does not: the NFSv3 data server path never checked, and the check on the NFSv4 path was removed when the data server stateid began to be taken from the layout.

Fail read and write RPCs to the data server in rpc_call_prepare when the lock is lost.

From the CVE Program. Shortened; the full text is there.

Affected software

SoftwareAffected versions
Linux kernelServers and applications · cna:linux|linux
  • From 4.0 before 6.12.117
  • From 6.13 before 6.18.61
  • From 6.19 before 7.3.2

About Linux kernel

Unix-like operating system kernel, basis for all Linux operating systems

From Wikidata, CC0 1.0.
GitHub stars
255,726GitHub, 15 Nov 2026
Forks
67,394GitHub, 15 Nov 2026
Developer
Linus TorvaldsWikidata
License
GNU General Public License, version 2.0Wikidata
Written in
CWikidata
First released
25 Aug 1991Wikidata
First published on GitHub
4 Sept 2011GitHub

References

  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-99375