CVE-2026-99373
Severity unknownNo known exploitationFix availableNFS/localio: detect a short read or write before the iterator has moved
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 13% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
In the Linux kernel, the following vulnerability has been resolved: NFS/localio: detect a short read or write before the iterator has moved nfs_local_call_read() and nfs_local_call_write() issue a misaligned DIO as up to three segments and must stop at the first short one, or the next segment lands at the wrong file offset. They test for that by comparing the bytes transferred against iov_iter_count() of the segment, read after read_iter() or write_iter() has advanced the iterator, when the count is the residual rather than the request: before the call: count == expected after the call: count == expected - status The test is therefore status < expected - status, and it fires only when less than half of the segment was transferred. A short I/O that covers between 50% and 99% of a segment slips through: the loop moves on with ki_pos advanced by the short amount, the next segment is issued at the wrong offset, and the header's byte count is over-reported to the caller. A write that slips through also never sets NFS_CONTEXT_WRITE_SYNC, which is what makes the writes that follow a short one synchronous. Take the segment's count before issuing it and compare against that. This is the same defect that commit 250ec14932d5 ("nfsd: fix partial-write detection in nfsd_direct_write") fixed in NFSD's version of this loop.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from c817248fc831f5494d076421672b70a6ec1a92dc before ca85441a75b526228923e2959bd576403c4bba85 | ca85441a75b526228923e2959bd576403c4bba85 | CVE Program |
| Linux | Linux | from c817248fc831f5494d076421672b70a6ec1a92dc before db3ca539c1142d2c5380c5dbd3154ab7bb1c7d77 | db3ca539c1142d2c5380c5dbd3154ab7bb1c7d77 | CVE Program |
| Linux | Linux | from c817248fc831f5494d076421672b70a6ec1a92dc before 8be28bd11e098cd4f109edca1b883fe5704167ee | 8be28bd11e098cd4f109edca1b883fe5704167ee | CVE Program |
| Linux | Linux | 6.18 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.64 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.2 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc1 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 6.18 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)