CVE-2026-31402

published 3 Apr 2026 · updated 12 Nov 2026

nfsd: fix heap overflow in NFSv4.0 LOCK replay cache

9.8CriticalCVSS 9.8EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 5.10.253, Kernel 6.1.167, Kernel 6.18.20 and 12 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=2.6.12.1 <5.10.253, >=5.11 <6.1.167, >=6.13 <6.18.20, >=6.19 <6.19.10, >=6.2 <6.6.130, >=6.7 <6.12.78, =2.6.12, =7.0, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2665887a69437a8a4f552f69509eecfb73d4aa19, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5133b61aaf437e5f25b1b396b14242a6bb0508e2, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8afb437ea1f70cacb4bbdf11771fb5c4d720b965, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ae8498337dfdfda71bdd0b807c9a23a126011d76, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c9452c0797c95cf2378170df96cf4f4b3bca7eff, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dad0c3c0a8e5d1d6eb0fc455694ce3e25e6c57d0, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f9fcb4441f6c02bb20c2eb340101e27dfe23607c, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0f0e2a54a31a7f9ad2915db991561148723173885.10.253, 6.1.167, 6.18.20, 6.19.10, 6.6.130, 6.12.78, 2665887a69437a8a4f552f69509eecfb73d4aa19, 5133b61aaf437e5f25b1b396b14242a6bb0508e2, 8afb437ea1f70cacb4bbdf11771fb5c4d720b965, ae8498337dfdfda71bdd0b807c9a23a126011d76, c9452c0797c95cf2378170df96cf4f4b3bca7eff, dad0c3c0a8e5d1d6eb0fc455694ce3e25e6c57d0, f9fcb4441f6c02bb20c2eb340101e27dfe23607c, 0f0e2a54a31a7f9ad2915db99156114872317388
linux-kernel: Kernel>=2.6.12 <5.10.253, >=5.11.0 <5.15.210, >=5.16.0 <6.1.167, >=6.13.0 <6.18.20, >=6.19.0 <6.19.10, >=6.2.0 <6.6.130, >=6.7.0 <6.12.785.10.253, 5.15.210, 6.1.167, 6.18.20, 6.19.10, 6.6.130, 6.12.78

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-31402 severity on Zeptric[![CVE-2026-31402](https://zeptric.io/badge/cve/CVE-2026-31402.svg)](https://zeptric.io/cve/CVE-2026-31402)