Skip to main content
VulnerabilityPublished

CVE-2026-99367: Linux kernel · NFSD: Don't complete a cld upcall the daemon has not read

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99367

Not known to be exploited · fixed in f6d1f1072243a1adb1ae15425f6e36f86be94078 : update Linux kernel when convenient.

Data as of 19 Nov 2026, 16:20 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f6d1f1072243a1adb1ae15425f6e36f86be94078, e058341ceb177226fdb20a36d48fa827851d9c81, 226c11eb20042ce4251f50870ce61f86581f8152 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Linux kernel to f6d1f1072243a1adb1ae15425f6e36f86be94078, e058341ceb177226fdb20a36d48fa827851d9c81, 226c11eb20042ce4251f50870ce61f86581f8152 or 7f4bf851aca4e18940ebf2bddf4ba6783802ee81.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ f3f8014862d813cca81a597c83bd1dbf0fb2b8f6, < f6d1f1072243a1adb1ae15425f6e36f86be94078
Fixed in
  • f6d1f1072243a1adb1ae15425f6e36f86be94078
LinuxLinuxAffected
  • ≥ f3f8014862d813cca81a597c83bd1dbf0fb2b8f6, < e058341ceb177226fdb20a36d48fa827851d9c81
Fixed in
  • e058341ceb177226fdb20a36d48fa827851d9c81
LinuxLinuxAffected
  • ≥ f3f8014862d813cca81a597c83bd1dbf0fb2b8f6, < 226c11eb20042ce4251f50870ce61f86581f8152
Fixed in
  • 226c11eb20042ce4251f50870ce61f86581f8152
LinuxLinuxAffected
  • ≥ f3f8014862d813cca81a597c83bd1dbf0fb2b8f6, < 7f4bf851aca4e18940ebf2bddf4ba6783802ee81
Fixed in
  • 7f4bf851aca4e18940ebf2bddf4ba6783802ee81
LinuxLinuxAffected
  • =3.4
Fixed in–

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.

References

Community reviews

Loading reviews…