CVE-2026-99375 (GCVE-0-2026-99375)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:23 – Updated: 2026-11-19 14:38| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
d67ae825a59d639e4d8b82413af84d854617a87e , < 88f3916a239fc945362eaac13ca2e29f59539f42
(git)
Affected: d67ae825a59d639e4d8b82413af84d854617a87e , < 938f374ec83912d1383810a1d31aa7ac1940b11e (git) Affected: d67ae825a59d639e4d8b82413af84d854617a87e , < fe52fa5319458d3d5f04046422b4cf954024a26f (git) Affected: d67ae825a59d639e4d8b82413af84d854617a87e , < 7fa2ad367abe6d3155daefb57331e7fce1a17afd (git) |
guessed | |
| Linux | Linux |
Affected:
4.0
Unaffected: 0 , < 4.0 (semver) Unaffected: 6.12.117 , ≤ 6.12.* (semver) Unaffected: 6.18.61 , ≤ 6.18.* (semver) Unaffected: 7.3.2 , ≤ 7.3.* (semver) Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/nfs/flexfilelayout/flexfilelayout.c",
"fs/nfs/nfs4_fs.h",
"fs/nfs/nfs4state.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "88f3916a239fc945362eaac13ca2e29f59539f42",
"status": "affected",
"version": "d67ae825a59d639e4d8b82413af84d854617a87e",
"versionType": "git"
},
{
"lessThan": "938f374ec83912d1383810a1d31aa7ac1940b11e",
"status": "affected",
"version": "d67ae825a59d639e4d8b82413af84d854617a87e",
"versionType": "git"
},
{
"lessThan": "fe52fa5319458d3d5f04046422b4cf954024a26f",
"status": "affected",
"version": "d67ae825a59d639e4d8b82413af84d854617a87e",
"versionType": "git"
},
{
"lessThan": "7fa2ad367abe6d3155daefb57331e7fce1a17afd",
"status": "affected",
"version": "d67ae825a59d639e4d8b82413af84d854617a87e",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/nfs/flexfilelayout/flexfilelayout.c",
"fs/nfs/nfs4_fs.h",
"fs/nfs/nfs4state.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.0"
},
{
"lessThan": "4.0",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.117",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.61",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.117",
"versionStartIncluding": "4.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.61",
"versionStartIncluding": "4.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.2",
"versionStartIncluding": "4.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "4.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/flexfiles: fail I/O to the data server once a lock is lost\n\nWhen a client loses a byte-range lock, because its lease expired and it\nmay not recover the lock (nfs.recover_lost_locks=0) or because reclaim\nfailed, it marks the lock state NFS_LOCK_LOST and fails further I/O by\nthat lock owner. Otherwise an application that believes it holds a\nlock over a range is never told that the lock is gone, and can\noverwrite data that another client has since written under its own\nlock on that range.\n\nThe NFSv4 READ/WRITE and file layout I/O paths apply this in\nrpc_call_prepare, where nfs4_set_rw_stateid() returns -EIO for a lost\nlock. The flexfiles data server I/O path does not: the NFSv3 data\nserver path never checked, and the check on the NFSv4 path was removed\nwhen the data server stateid began to be taken from the layout.\n\nFail read and write RPCs to the data server in rpc_call_prepare when the\nlock is lost. The data server path has no use for the stateid that\nnfs4_set_rw_stateid() selects, and selecting it looks up a delegation\nor open stateid on every I/O.\nInstead add nfs4_lock_context_lost(), which only tests NFS_LOCK_LOST,\nand check it alongside the open state. Its lookup,\n__nfs4_lookup_lock_state(), is split out of __nfs4_find_lock_state()\nand takes no reference: a lock state is only unlinked from\nstate-\u003elock_states under state-\u003estate_lock, so one found while holding\nthat lock cannot be freed before it is released. Use it in\nnfs4_copy_lock_stateid() as well, which only reads the lock state under\nthat lock. That drops a reference get and put from stateid selection\nfor all NFSv4 I/O without changing the stateid selected.\n\nTerminating the RPC in rpc_call_prepare is not enough on its own. The\ndone callback reads the -EIO as a data server connection error, forgets\nthe device ID, and resets the I/O to pNFS (or, for an NFSv4 data\nserver, possibly to the MDS). After a reset to pNFS a new LAYOUTGET is\ngranted and rpc_call_prepare fails the I/O again, without end. The\nexisting NFS_CONTEXT_BAD check does not loop, since the open state is\nthen invalid and pnfs_update_layout() fails the reset I/O, but it still\nforgets the device ID.\n\nSo when an RPC that was never sent fails and the open context is bad,\nthe open state is invalid, or the lock is lost, complete it with -EIO\nwithout error handling. An RPC that was sent and failed is handled as\nbefore, so a real data server error is still reported to the MDS."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:38:09.738Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/88f3916a239fc945362eaac13ca2e29f59539f42"
},
{
"url": "https://git.kernel.org/stable/c/938f374ec83912d1383810a1d31aa7ac1940b11e"
},
{
"url": "https://git.kernel.org/stable/c/fe52fa5319458d3d5f04046422b4cf954024a26f"
},
{
"url": "https://git.kernel.org/stable/c/7fa2ad367abe6d3155daefb57331e7fce1a17afd"
}
],
"title": "NFSv4/flexfiles: fail I/O to the data server once a lock is lost",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99375",
"datePublished": "2026-11-19T14:23:11.576Z",
"dateReserved": "2026-09-25T10:25:14.411Z",
"dateUpdated": "2026-11-19T14:38:09.738Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99375",
"date": "2026-11-20",
"epss": "0.00224",
"percentile": "0.13373"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/nfs/flexfilelayout/flexfilelayout.c",
"fs/nfs/nfs4_fs.h",
"fs/nfs/nfs4state.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "88f3916a239fc945362eaac13ca2e29f59539f42",
"status": "affected",
"version": "d67ae825a59d639e4d8b82413af84d854617a87e",
"versionType": "git"
},
{
"lessThan": "938f374ec83912d1383810a1d31aa7ac1940b11e",
"status": "affected",
"version": "d67ae825a59d639e4d8b82413af84d854617a87e",
"versionType": "git"
},
{
"lessThan": "fe52fa5319458d3d5f04046422b4cf954024a26f",
"status": "affected",
"version": "d67ae825a59d639e4d8b82413af84d854617a87e",
"versionType": "git"
},
{
"lessThan": "7fa2ad367abe6d3155daefb57331e7fce1a17afd",
"status": "affected",
"version": "d67ae825a59d639e4d8b82413af84d854617a87e",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/nfs/flexfilelayout/flexfilelayout.c",
"fs/nfs/nfs4_fs.h",
"fs/nfs/nfs4state.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.0"
},
{
"lessThan": "4.0",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.117",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.61",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/flexfiles: fail I/O to the data server once a lock is lost\n\nWhen a client loses a byte-range lock, because its lease expired and it\nmay not recover the lock (nfs.recover_lost_locks=0) or because reclaim\nfailed, it marks the lock state NFS_LOCK_LOST and fails further I/O by\nthat lock owner. Otherwise an application that believes it holds a\nlock over a range is never told that the lock is gone, and can\noverwrite data that another client has since written under its own\nlock on that range.\n\nThe NFSv4 READ/WRITE and file layout I/O paths apply this in\nrpc_call_prepare, where nfs4_set_rw_stateid() returns -EIO for a lost\nlock. The flexfiles data server I/O path does not: the NFSv3 data\nserver path never checked, and the check on the NFSv4 path was removed\nwhen the data server stateid began to be taken from the layout.\n\nFail read and write RPCs to the data server in rpc_call_prepare when the\nlock is lost. The data server path has no use for the stateid that\nnfs4_set_rw_stateid() selects, and selecting it looks up a delegation\nor open stateid on every I/O.\nInstead add nfs4_lock_context_lost(), which only tests NFS_LOCK_LOST,\nand check it alongside the open state. Its lookup,\n__nfs4_lookup_lock_state(), is split out of __nfs4_find_lock_state()\nand takes no reference: a lock state is only unlinked from\nstate-\u003elock_states under state-\u003estate_lock, so one found while holding\nthat lock cannot be freed before it is released. Use it in\nnfs4_copy_lock_stateid() as well, which only reads the lock state under\nthat lock. That drops a reference get and put from stateid selection\nfor all NFSv4 I/O without changing the stateid selected.\n\nTerminating the RPC in rpc_call_prepare is not enough on its own. The\ndone callback reads the -EIO as a data server connection error, forgets\nthe device ID, and resets the I/O to pNFS (or, for an NFSv4 data\nserver, possibly to the MDS). After a reset to pNFS a new LAYOUTGET is\ngranted and rpc_call_prepare fails the I/O again, without end. The\nexisting NFS_CONTEXT_BAD check does not loop, since the open state is\nthen invalid and pnfs_update_layout() fails the reset I/O, but it still\nforgets the device ID.\n\nSo when an RPC that was never sent fails and the open context is bad,\nthe open state is invalid, or the lock is lost, complete it with -EIO\nwithout error handling. An RPC that was sent and failed is handled as\nbefore, so a real data server error is still reported to the MDS."
}
],
"id": "CVE-2026-99375",
"lastModified": "2026-11-19T15:17:49.440",
"metrics": {},
"published": "2026-11-19T15:17:49.440",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7fa2ad367abe6d3155daefb57331e7fce1a17afd"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/88f3916a239fc945362eaac13ca2e29f59539f42"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/938f374ec83912d1383810a1d31aa7ac1940b11e"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/fe52fa5319458d3d5f04046422b4cf954024a26f"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Low",
"current_release_date": "2026-11-19T21:05:43+00:00",
"cve": "CVE-2026-99375",
"id": "CVE-2026-99375",
"initial_release_date": "2026-11-19T14:23:11.576000+00:00",
"product_status:known_affected": "204",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Data corruption via missing lock validation in NFS flexfiles client",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99375.json",
"version": "3"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.