CVE-2026-31402: Linux kernel · nfsd: fix heap overflow in NFSv4.0 LOCK replay cache
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 9.8 Critical · fixed in 3.13.0-214.265 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 67% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.13.0-214.265, 4.4.0-1156.162, 4.15.0-1205.220~14.04.1 +122
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-8490-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8491-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8493-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8497-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8498-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8499-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8493-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8501-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8508-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-3 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 25.10linuxpkg:deb/ubuntu/linux?arch=source&distro=questingOther threats | Affected
| Fixed in
|
Ubuntu 25.10linux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=questingOther threats | Affected
| Fixed in
|
Ubuntu 25.10linux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=questingOther threats | Affected
| Fixed in
|
Ubuntu 25.10linux-oraclepkg:deb/ubuntu/linux-oracle?arch=source&distro=questingOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting lock to provoke the denial. We could fix this by increasing NFSD4_REPLAY_ISIZE to allow for a full opaque, but that would increase the size of every stateowner, when most lockowners are not that large. Instead, fix this by checking the encoded response length against NFSD4_REPLAY_ISIZE before copying into the replay buffer. If the response is too large, set rp_buflen to 0 to skip caching the replay payload. The status is still cached, and the client already received the correct response on the original request.
References
- ubuntu.com/security/CVE-2026-31402 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-31402 (opens in a new tab)
- git.kernel.org/linus/5133b61aaf437e5f25b1b396b14242a6bb0508e2 (opens in a new tab)
- git.kernel.org/stable/c/0f0e2a54a31a7f9ad2915db99156114872317388 (opens in a new tab)
- git.kernel.org/stable/c/5133b61aaf437e5f25b1b396b14242a6bb0508e2 (opens in a new tab)
- git.kernel.org/stable/c/8afb437ea1f70cacb4bbdf11771fb5c4d720b965 (opens in a new tab)
- git.kernel.org/stable/c/ae8498337dfdfda71bdd0b807c9a23a126011d76 (opens in a new tab)
- git.kernel.org/stable/c/c9452c0797c95cf2378170df96cf4f4b3bca7eff (opens in a new tab)
- git.kernel.org/stable/c/dad0c3c0a8e5d1d6eb0fc455694ce3e25e6c57d0 (opens in a new tab)
- ubuntu.com/security/notices/USN-8490-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8491-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8493-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8497-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8498-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8499-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8493-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8501-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8508-1 (opens in a new tab)