Search for packages
| purl | pkg:rpm/redhat/kernel@5.14.0-427.121.1?arch=el9_4 |
| Next non-vulnerable version | None. |
| Latest non-vulnerable version | None. |
| Risk | 3.5 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-4y9e-89wb-gbaz
Aliases: CVE-2026-23111 |
kernel: Kernel: Privilege escalation or denial of service in nf_tables via inverted element activity check | There are no reported fixed by versions. |
|
VCID-6u26-3zuf-xqee
Aliases: CVE-2025-68800 |
kernel: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats | There are no reported fixed by versions. |
|
VCID-9kuz-7fag-4qhv
Aliases: CVE-2026-23231 |
kernel: kernel: Privilege escalation or denial of service via use-after-free in nf_tables_addchain() | There are no reported fixed by versions. |
|
VCID-dt7e-edy8-d3b4
Aliases: CVE-2026-23144 |
kernel: Linux kernel: Local denial of service and memory leak in DAMON sysfs via setup failure | There are no reported fixed by versions. |
|
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-ptyj-1y6d-dud1
Aliases: CVE-2026-23066 |
kernel: Linux kernel: Denial of Service via unsafe requeue in rxrpc_recvmsg | There are no reported fixed by versions. |
|
VCID-r4zk-9j6t-uyhg
Aliases: CVE-2025-39981 |
kernel: Bluetooth: MGMT: Fix possible UAFs | There are no reported fixed by versions. |
|
VCID-th3e-y2nm-u7eh
Aliases: CVE-2026-23193 |
kernel: scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() | There are no reported fixed by versions. |
|
VCID-u6nn-wr8u-qqdj
Aliases: CVE-2026-23171 |
kernel: Linux kernel: Use-after-free in bonding module can cause system crash or arbitrary code execution | There are no reported fixed by versions. |
|
VCID-vsyg-x46t-ayhz
Aliases: CVE-2026-23204 |
kernel: net/sched: cls_u32: use skb_header_pointer_careful() | 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. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||