Staging Environment: Content and features may be unstable or change without notice.
Search for packages
Package details: pkg:rpm/redhat/kernel@5.14.0-570.110.1?arch=el9_6
purl pkg:rpm/redhat/kernel@5.14.0-570.110.1?arch=el9_6
Next non-vulnerable version None.
Latest non-vulnerable version None.
Risk
Vulnerabilities affecting this package (2)
Vulnerability Summary Fixed by
VCID-kvbv-df49-gyaj
Aliases:
CVE-2026-31402
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. There are no reported fixed by versions.
VCID-xkg2-9n6y-5kan
Aliases:
CVE-2026-23097
kernel: Linux kernel: Denial of Service due to a deadlock in hugetlb folio migration There are no reported fixed by versions.
Vulnerabilities fixed by this package (0)
Vulnerability Summary Aliases
This package is not known to fix vulnerabilities.

Date Actor Action Vulnerability Source VulnerableCode Version
2026-04-29T12:58:53.802124+00:00 RedHat Importer Affected by VCID-xkg2-9n6y-5kan https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-23097.json 38.5.0
2026-04-29T12:58:38.307469+00:00 RedHat Importer Affected by VCID-kvbv-df49-gyaj https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-31402.json 38.5.0