Heap overflow in Linux kernel nfsd NFSv4.0 LOCK replay cache
CVE-2026-31402 is a heap-based buffer overflow in the Linux kernel NFS server (nfsd), specifically in the NFSv4.0 LOCK replay cache. The replay cache stores encoded operation responses in a fixed 112-byte inline buffer, rp_ibuf[NFSD4_REPLAY_ISIZE], whose size was derived from OPEN responses. However, denied LOCK responses can include a conflicting lock owner field with variable length up to NFS4_OPAQUE_LIMIT (1024 bytes). When a LOCK request is denied because of a conflicting existing lock with a large owner string, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() without adequate bounds checking. This can produce a slab out-of-bounds write of up to 944 bytes past the end of the heap buffer, corrupting adjacent kernel heap memory.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
16 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.