nfsd: fix heap overflow in NFSv4.0 LOCK replay cache
Summary
| CVE | CVE-2026-31402 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-04-03 16:16:39 UTC |
| Updated | 2026-04-03 16:16:39 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 c9452c0797c95cf2378170df96cf4f4b3bca7eff git |
Not specified |
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 8afb437ea1f70cacb4bbdf11771fb5c4d720b965 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 dad0c3c0a8e5d1d6eb0fc455694ce3e25e6c57d0 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 0f0e2a54a31a7f9ad2915db99156114872317388 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 ae8498337dfdfda71bdd0b807c9a23a126011d76 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 5133b61aaf437e5f25b1b396b14242a6bb0508e2 git |
Not specified |
| CNA |
Linux |
Linux |
affected 2.6.12 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 2.6.12 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.167 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.130 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.78 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.20 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.19.10 6.19.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0-rc5 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/5133b61aaf437e5f25b1b396b14242a6bb0508e2 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/8afb437ea1f70cacb4bbdf11771fb5c4d720b965 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/dad0c3c0a8e5d1d6eb0fc455694ce3e25e6c57d0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/0f0e2a54a31a7f9ad2915db99156114872317388 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c9452c0797c95cf2378170df96cf4f4b3bca7eff |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ae8498337dfdfda71bdd0b807c9a23a126011d76 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.