Testing Blog

CVE-2026-99362: Linux Kernel nfsd Out-of-Bounds… | Uptycs

Written by Uptycs Threat Research | Nov 20, 2026, 1:00:11 PM
CVE IDCVE-2026-99362
Affected productLinux
SeverityHigh CVSS n/a (v3.1)
ExploitationNo known exploitation
CISA KEVNot listed
Fix availableYes
Bulletin statusAnalysis complete · Last updated 2026-11-20

Key takeaways

  • Affects Linux kernel ≥ commit 47ee5298 (introducing the vulnerable code path), all versions up to the following fixed commits.
  • No known exploitation yet: patch before attackers catch up.
  • Upgrade the Linux kernel to version 6.12.117, 6.18.61, 7.3.2, or 7.4-rc1 (mainline), or apply the fixed commits (1a5a227b, 37fc2ec2, ed98b0c5, 35ff1a7a) appropriate for your kernel branch.

Summary

CVE-2026-99362 is an out-of-bounds write vulnerability in the Linux kernel's NFSv4 server implementation (nfsd). The flaw exists in the handling of NFSv4 SEQUENCE operations within COMPOUND requests, where a logic error allows data to be written beyond the bounds of a zero-length slot cache buffer. An unauthenticated, remote attacker who can send crafted NFSv4 COMPOUND requests to an affected server may be able to corrupt kernel memory, with potential impact to confidentiality, integrity, and availability. The vulnerability was published on 19 November 2026, and fixes are available in multiple stable kernel branches.

Technical details

The root cause lies in nfsd4_sequence(), which narrows the reply buffer to the session's cached reply limit before it validates the slot sequence ID. A client can negotiate ca_maxresponsesize_cached down to NFSD_MIN_HDR_SEQ_SZ, causing nfsd4_alloc_slot() to allocate a zero-length sl_data[] buffer for every slot. If a COMPOUND tag fills the narrowed buffer up to but not past the SEQUENCE opcode, nfsd4_encode_operation() returns without encoding the SEQUENCE result, leaving cstate.data_offset at zero and the operation status as nfs_ok. The subsequent cache-store logic then copies the entire reply — RPC and COMPOUND headers included — starting at offset zero into the zero-length slot buffer, producing a slab-out-of-bounds write.

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects that exploitation requires no authentication, no user interaction, and no special configuration beyond an exposed NFSv4 server. Any system running nfsd and reachable over the network is a potential target. The exact conditions needed to reliably control the out-of-bounds write to achieve code execution have not been confirmed publicly.

Affected products

Product / branchAffected versionsFixed version
Linux kernel≥ commit 47ee5298 (introducing the vulnerable code path), all versions up to the following fixed commitscommits 1a5a227b, 37fc2ec2, ed98b0c5, 35ff1a7a
Linux kernel3.16 through 6.12.1166.12.117
Linux kernelthrough 6.18.606.18.61
Linux kernelthrough 7.3.17.3.2
Linux kernel7.4-rc1 and later development builds — fix available in mainlineSee vendor advisory

Impact

  • Kernel memory corruption: The out-of-bounds write overwrites slab memory beyond a zero-length slot cache buffer, which can destabilize or crash the kernel.
  • Potential privilege escalation or code execution: Memory corruption in a kernel context can, depending on heap layout, be leveraged to execute arbitrary code with kernel privileges.
  • Data exposure: The CVSS score reflects high confidentiality impact; corrupted or misread cache entries could expose sensitive kernel or NFS session data.
  • Denial of service: Even without full exploitation, triggering the bug can cause a kernel panic or system crash, disrupting NFS services and dependent workloads.

Exploitation status

As of 2026-11-20, no in-the-wild exploitation has been confirmed as of this bulletin, and no public proof-of-concept code has been identified. The vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities catalog. Despite the absence of active exploitation, the critical CVSS score and unauthenticated network attack vector make this a high-priority patching target for any system running the Linux NFSv4 server.

Recommendations

  1. Upgrade the Linux kernel: to version 6.12.117, 6.18.61, 7.3.2, or 7.4-rc1 (mainline), or apply the fixed commits (1a5a227b, 37fc2ec2, ed98b0c5, 35ff1a7a) appropriate for your kernel branch.
  2. If patching is not immediately possible: , disable the NFSv4 server (nfsd) on systems where it is not required, or restrict NFS access to trusted hosts using firewall rules blocking TCP/UDP port 2049 from untrusted networks.
  3. Audit NFSv4 server exposure: confirm whether systems running nfsd are reachable from untrusted network segments and restrict access accordingly.
  4. Verify the fix: by checking the running kernel version (uname -r) against the fixed versions listed above after applying updates.
  5. Review NFS server logs: for unusual COMPOUND request patterns, unexpected kernel warnings (KASAN output), or slab-out-of-bounds messages in dmesg that may indicate prior exploitation attempts.

How Uptycs helps

Uptycs vulnerability management continuously inventories hosts, containers, and cloud workloads running affected kernel versions, enabling security teams to identify and prioritize patching across their entire environment. Uptycs Threat Research continues to monitor CVE-2026-99362 for changes in exploitation activity and will update this bulletin if new evidence emerges.

References

Update history

  • 2026-11-20: Initial publication.

See how Uptycs finds affected assets across your hybrid cloud.

Get a demo
White Paper

Verifiable AI: The Foundation for Trust in Cybersecurity

Download copy

Index