CVE-2026-99362: Linux kernel · nfsd: preflight SEQUENCE replies before accepting a slot
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ed98b0c57e5e84290c5b35428144ab26778905f3 : update Linux kernel when convenient.
Data as of 19 Nov 2026, 14:34 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in ed98b0c57e5e84290c5b35428144ab26778905f3, 37fc2ec211630360e9aefcaaec8730db964645f2, 35ff1a7a7e3835c3e974bc5c45d335897564ceae +1
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 ed98b0c57e5e84290c5b35428144ab26778905f3, 37fc2ec211630360e9aefcaaec8730db964645f2, 35ff1a7a7e3835c3e974bc5c45d335897564ceae or 1a5a227bca6a8a9f9d31230697aeb84c62a21da6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: nfsd: preflight SEQUENCE replies before accepting a slot nfsd4_sequence() narrows the reply buffer to the session's cached reply limit before it accepts the slot seqid. A client may negotiate ca_maxresponsesize_cached down to NFSD_MIN_HDR_SEQ_SZ, and nfsd4_alloc_slot() then gives every slot a zero-length sl_data[]. A COMPOUND tag can fill that narrowed buffer until it holds the SEQUENCE opcode but not the status word that follows. nfsd4_encode_operation() returns without running nfsd4_encode_sequence(), so cstate.data_offset stays zero. It leaves op->status at nfs_ok as well, so the COMPOUND is treated as having succeeded. nfsd4_store_cache_entry() declines to cache a lone SEQUENCE that returned an error. That test reads the status the operation reported, so it passes here. The copy starts at offset zero and takes the whole reply, RPC and COMPOUND headers included, into the zero-length sl_data[]. The COMPOUND tag is copied along with it, so the client picks most of the bytes written past the end of the slot: BUG: KASAN: slab-out-of-bounds in read_bytes_from_xdr_buf+0x1bc/0x390 Write of size 80 at addr ffff888003a549cd by task kunit_try_catch/24 __asan_memcpy+0x38/0x60 read_bytes_from_xdr_buf+0x1bc/0x390 nfsd4_sequence_done+0x5b0/0x810 nfs4svc_encode_compoundres+0x1bf/0x240 Check that the fixed-size SEQUENCE result, plus room for a following operation's error status, fits the negotiated limit before narrowing the buffer and consuming the slot seqid. The slot and its reply cache are left unchanged, as RFC 8881 Section 2.10.6.1.2 requires of an error returned from SEQUENCE.
References
- git.kernel.org/stable/c/1a5a227bca6a8a9f9d31230697aeb84c62a21da6 (opens in a new tab)
- git.kernel.org/stable/c/37fc2ec211630360e9aefcaaec8730db964645f2 (opens in a new tab)
- git.kernel.org/stable/c/ed98b0c57e5e84290c5b35428144ab26778905f3 (opens in a new tab)
- git.kernel.org/stable/c/35ff1a7a7e3835c3e974bc5c45d335897564ceae (opens in a new tab)