CVE-2026-99367
Severity unknownNo known exploitationFix availableNFSD: Don't complete a cld upcall the daemon has not read
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 11% 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: NFSD: Don't complete a cld upcall the daemon has not read cld_pipe_downcall() matches a reply to its upcall on the xid alone. A write that arrives before the daemon has read that upcall completes __cld_pipe_upcall() while its struct rpc_pipe_msg is still queued on the pipe. The waiter returns, its stack frame goes away, and the pipe keeps a list_head that points into it. The next rpc_queue_upcall() walks that pointer: BUG: KASAN: vmalloc-out-of-bounds in __list_add_valid_or_report Read of size 8 at addr ffffc90007027950 by task syz.0.96/13066 __list_add_valid_or_report+0x6a/0x130 rpc_queue_upcall cld_pipe_upcall nfsd4_cld_grace_start nfsd4_cld_tracking_init The pipe is mode 0600 in rpc_pipefs, so the trigger is a broken or hostile nfsdcld rather than an unprivileged task. Record whether the daemon has consumed the whole message and complete only when it has. cld_pipe_destroy_msg() runs on every path by which the pipe releases a message, so it can maintain that flag under cn_lock. nfsdcld sends its -EINPROGRESS downcalls only after reading the upcall, so the new check does not break the GraceStart record stream.
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 f3f8014862d813cca81a597c83bd1dbf0fb2b8f6 before f6d1f1072243a1adb1ae15425f6e36f86be94078 | f6d1f1072243a1adb1ae15425f6e36f86be94078 | CVE Program |
| Linux | Linux | from f3f8014862d813cca81a597c83bd1dbf0fb2b8f6 before 226c11eb20042ce4251f50870ce61f86581f8152 | 226c11eb20042ce4251f50870ce61f86581f8152 | CVE Program |
| Linux | Linux | from f3f8014862d813cca81a597c83bd1dbf0fb2b8f6 before 7f4bf851aca4e18940ebf2bddf4ba6783802ee81 | 7f4bf851aca4e18940ebf2bddf4ba6783802ee81 | CVE Program |
| Linux | Linux | from f3f8014862d813cca81a597c83bd1dbf0fb2b8f6 before e058341ceb177226fdb20a36d48fa827851d9c81 | e058341ceb177226fdb20a36d48fa827851d9c81 | CVE Program |
| Linux | Linux | 3.4 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.117 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.61 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 3.4 | 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)
Vendor guidance and references
- https://git.kernel.org/stable/c/226c11eb20042ce4251f50870ce61f86581f8152 (opens in a new tab)
- https://git.kernel.org/stable/c/7f4bf851aca4e18940ebf2bddf4ba6783802ee81 (opens in a new tab)
- https://git.kernel.org/stable/c/e058341ceb177226fdb20a36d48fa827851d9c81 (opens in a new tab)
- https://git.kernel.org/stable/c/f6d1f1072243a1adb1ae15425f6e36f86be94078 (opens in a new tab)