Linux kernel out-of-bounds write in NFSD SEQUENCE reply handling
Affects the Linux kernel NFS server (nfsd) handling NFSv4.1 sessions when a client negotiates the minimum cached reply size. No vendor rating is given; fixed by kernel commits 1a5a227bca6a, 37fc2ec21163, ed98b0c57e5e and 35ff1a7a7e38.
- Exploited
- No known exploitation
- Fix
- Vendor patch: 1a5a227bca6a8a9f9d31230697aeb84c62a21da6, 37fc2ec211630360e9aefcaaec8730db964645f2, ed98b0c57e5e84290c5b35428144ab26778905f3, 35ff1a7a7e3835c3e974bc5c45d335897564ceae
- Who is exposed
- Not reported
Summary
The Linux kernel's nfsd server component has a flaw in how it handles SEQUENCE replies with a negotiated small cached reply size. A client can trigger an out-of-bounds write in kernel memory, and the client can read back part of the data written past the end of the buffer.
Written by a model
Original 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.
Who should check
Teams running the Linux kernel NFS server (nfsd) with NFSv4.1 sessions, exposed to clients on the network. Kernel and storage teams should check for the nfsd fix.
“nfsd4_sequence() narrows the reply buffer to the session's cached reply limit before it accepts the slot seqid.”
What to do
Apply the vendor's patch: 1a5a227bca6a8a9f9d31230697aeb84c62a21da6, 37fc2ec211630360e9aefcaaec8730db964645f2, ed98b0c57e5e84290c5b35428144ab26778905f3, 35ff1a7a7e3835c3e974bc5c45d335897564ceae.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99362 (nfsd: preflight SEQUENCE replies before accepting a slot), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99362 (entry last updated 2026-11-22):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 3.16
Vendor patches: 1a5a227bca6a8a9f9d31230697aeb84c62a21da6, 37fc2ec211630360e9aefcaaec8730db964645f2, ed98b0c57e5e84290c5b35428144ab26778905f3, 35ff1a7a7e3835c3e974bc5c45d335897564ceae (source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1a5a227bca6a8a9f9d31230697aeb84c62a21da6). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- Linux kernel NFS server (nfsd) handling NFSv4.1 sessions (source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1a5a227bca6a8a9f9d31230697aeb84c62a21da6)
- Client negotiates the cached response size down to the minimum, so every slot gets a zero-length reply buffer (source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1a5a227bca6a8a9f9d31230697aeb84c62a21da6)
- A COMPOUND tag fills the narrowed reply buffer so it holds the SEQUENCE opcode but not its status word (source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1a5a227bca6a8a9f9d31230697aeb84c62a21da6)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-99362 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99362 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/1a5a227bca6a8a9f9d31230697aeb84c62a21da6
- https://git.kernel.org/stable/c/37fc2ec211630360e9aefcaaec8730db964645f2
- https://git.kernel.org/stable/c/ed98b0c57e5e84290c5b35428144ab26778905f3
- https://git.kernel.org/stable/c/35ff1a7a7e3835c3e974bc5c45d335897564ceae
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1a5a227bca6a8a9f9d31230697aeb84c62a21da6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99362
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99362"}.Affected versions
- Linux LinuxVersion range not reported
- Linux Linux3.16
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity9.8/10CVSS 9.8
- No patch0/5No signal
What would change the score
- Would score about 92 if added to CISA KEV
- Would score about 87 if CISA's SSVC rates exploitation active
- Would score about 52 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now3 days
- Record last updated
- Posted on X by cve.now
Public exploit activity
- EPSS: 0.23%
- Posted on X by cve.now Nov 22
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99362 |
| Record | NVD · CVE-2026-99362 |
| Other links 4 | |
| Link | git.kernel.org · stable/c/1a5a227bca6a8a9f9d31230697aeb84c62a21da6 |
| Link | git.kernel.org · stable/c/37fc2ec211630360e9aefcaaec8730db964645f2 |
| Link | git.kernel.org · stable/c/ed98b0c57e5e84290c5b35428144ab26778905f3 |
| Link | git.kernel.org · stable/c/35ff1a7a7e3835c3e974bc5c45d335897564ceae |
Questions about CVE-2026-99362
Is CVE-2026-99362 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The Linux NFS server could write a reply into a zero-length slot buffer without first checking that the reply fits. A remote client could cause an out-of-bounds write in kernel slab memory with mostly client-chosen bytes, and read adjacent slab memory back. This can crash the nfsd thread or the host.
Source: git.kernel.org
Which versions are affected by CVE-2026-99362?
Linux: version 3.16.
Source: cve.now feed data
Am I affected, and how do I check?
The facts describe the Linux kernel NFS server (nfsd) handling NFSv4.1 sessions. The problem arises when a client negotiates the cached response size down to the minimum, so every slot gets a zero-length reply buffer, and a COMPOUND tag fills the narrowed buffer. No version ranges are listed, so check the running kernel version with uname -r and compare it against the vendor's or distribution's fix information for the listed commits.
Source: git.kernel.org
How do I fix CVE-2026-99362?
No fixed version numbers are named. The fix is in the kernel commits 1a5a227bca6a8a9f9d31230697aeb84c62a21da6, 37fc2ec211630360e9aefcaaec8730db964645f2, ed98b0c57e5e84290c5b35428144ab26778905f3 and 35ff1a7a7e3835c3e974bc5c45d335897564ceae. Apply a kernel update that includes them. No workaround is given.
Source: git.kernel.org
Related
- CVE-2026-99792smb/server: prevent file publication after tree disconnect
- CVE-2026-99794Bluetooth: L2CAP: Reject signalling responses in invalid states
- CVE-2026-99793Bluetooth: L2CAP: Only accept connection responses to outstanding requests
- CVE-2026-99804io_uring/io-wq: save worker type before dropping its reference
- CVE-2026-99800io_uring: free the task context after a grace period
- CVE-2026-99798io_uring: defer foreign io-wq enqueues to task_work
No corrections so far. Something wrong on this page? Report an error.