CVE-2026-31402 remediation guide

Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support

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...

Open CVE record

ProductLinux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support

Affected versions>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < f9fcb4441f6c02bb20c2eb340101e27dfe23607c, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 2665887a69437a8a4f552f69509eecfb73d4aa19, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < c9452c0797c95cf2378170df96cf4f4b3bca7eff, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 8afb437ea1f70cacb4bbdf11771fb5c4d720b965, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < dad0c3c0a8e5d1d6eb0fc455694ce3e25e6c57d0, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0f0e2a54a31a7f9ad2915db99156114872317388, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ae8498337dfdfda71bdd0b807c9a23a126011d76, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5133b61aaf437e5f25b1b396b14242a6bb0508e2, >= 2.6.12, >= V3.1.6, >= V3.1.5, >= 2.6.12.1 < 5.10.253, >= 5.11 < 6.1.167, >= 6.2 < 6.6.130, >= 6.7 < 6.12.78, >= 6.13 < 6.18.20, >= 6.19 < 6.19.10, 2.6.12, 7.0

Fixed versions5.10.253, 6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10

Priority basisReview · CVSS 9.8 · EPSS 0.49%

Identify the affected asset

Confirm whether Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < f9fcb4441f6c02bb20c2eb340101e27dfe23607c, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 2665887a69437a8a4f552f69509eecfb73d4aa19, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < c9452c0797c95cf2378170df96cf4f4b3bca7eff, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 8afb437ea1f70cacb4bbdf11771fb5c4d720b965, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < dad0c3c0a8e5d1d6eb0fc455694ce3e25e6c57d0, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0f0e2a54a31a7f9ad2915db99156114872317388, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ae8498337dfdfda71bdd0b807c9a23a126011d76, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5133b61aaf437e5f25b1b396b14242a6bb0508e2, >= 2.6.12, >= V3.1.6, >= V3.1.5, >= 2.6.12.1 < 5.10.253, >= 5.11 < 6.1.167, >= 6.2 < 6.6.130, >= 6.7 < 6.12.78, >= 6.13 < 6.18.20, >= 6.19 < 6.19.10, 2.6.12, 7.0. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 5.10.253, 6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10. Preserve configuration and rollback material before change.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.