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

Published Nov 19, 2026
·
Updated

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

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

When a client loses a byte-range lock, because its lease expired and it may not recover the lock (nfs.recoverlostlocks=0) or because reclaim failed, it marks the lock state NFSLOCKLOST 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 rpccallprepare, where nfs4setrwstateid() 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 rpccallprepare when the lock is lost. The data server path has no use for the stateid that nfs4setrwstateid() selects, and selecting it looks up a delegation or open stateid on every I/O. Instead add nfs4lockcontextlost(), which only tests NFSLOCKLOST, and check it alongside the open state. Its lookup, nfs4lookuplockstate(), is split out of nfs4findlockstate() and takes no reference: a lock state is only unlinked from state->lockstates under state->statelock, so one found while holding that lock cannot be freed before it is released. Use it in nfs4copylockstateid() as well, which only reads the lock state under that lock. That drops a reference get and put from stateid selection for all NFSv4 I/O without changing the stateid selected.

Terminating the RPC in rpccallprepare is not enough on its own. The done callback reads the -EIO as a data server connection error, forgets the device ID, and resets the I/O to pNFS (or, for an NFSv4 data server, possibly to the MDS). After a reset to pNFS a new LAYOUTGET is granted and rpccallprepare fails the I/O again, without end. The existing NFSCONTEXTBAD check does not loop, since the open state is then invalid and pnfsupdatelayout() fails the reset I/O, but it still forgets the device ID.

So when an RPC that was never sent fails and the open context is bad, the open state is invalid, or the lock is lost, complete it with -EIO without error handling. An RPC that was sent and failed is handled as before, so a real data server error is still reported to the MDS.

Affected Software

3 affected componentsFixes available
linux/kernel>=4.0.0<6.12.117
6.12.117
linux/kernel>=6.13.0<6.18.61
6.18.61
linux/kernel>=6.19.0<7.3.2
7.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.117
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.61
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2

Event History

Nov 19, 2026
CVE Published
via MITRE·02:23 PM
Data Sourced
via MITRE·02:23 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203