rpm package
almalinux/kernel-64k-modules
pkg:rpm/almalinux/kernel-64k-modules
Vulnerabilities (1,406)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-63823 | Hig | 7.8 | < 5.14.0-687.50.1.el9_8 | 5.14.0-687.50.1.el9_8 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: keys: Pin request_key_auth payload in instantiate paths A: request_key() B: KEYCTL_INSTANTIATE_IOV ================ ========================= create auth key store rka in auth key wait for helper | |
| CVE-2026-63808 | Cri | 9.8 | < 5.14.0-687.44.1.el9_8 | 5.14.0-687.44.1.el9_8 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: exfat: fix potential use-after-free in exfat_find_dir_entry() In exfat_find_dir_entry(), the buffer_head obtained from exfat_get_dentry() is released with brelse(bh) before the fall-through TYPE_EXTEND branch r | |
| CVE-2026-63802 | Hig | 7.8 | < 5.14.0-687.51.1.el9_8 | 5.14.0-687.51.1.el9_8 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix UAF in __blkcg_rstat_flush() When multiple blkgs in the same blkcg are released concurrently, a use-after-free can occur. The race happens when one blkg's __blkcg_rstat_flush() removes another b | |
| CVE-2026-63801 | Hig | 8.8 | < 5.14.0-687.47.1.el9_8 | 5.14.0-687.47.1.el9_8 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done tipc_aead_decrypt() goes straight from tipc_bearer_hold(b) to crypto_aead_decrypt(req) without taking a reference on the netns, unlike the encrypt pa | |
| CVE-2026-63800 | Cri | 9.8 | < 5.14.0-687.44.1.el9_8 | 5.14.0-687.44.1.el9_8 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: pNFS: Fix use-after-free in pnfs_update_layout() When hitting the NFS_LAYOUT_RETURN branch in pnfs_update_layout(), the code calls pnfs_prepare_to_retry_layoutget(lo). If it succeeds, pnfs_put_layout_hdr(lo) is | |
| CVE-2026-63794 | Hig | 7.8 | < 5.14.0-687.54.1.el9_8 | 5.14.0-687.54.1.el9_8 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Fix page overflow in sev_dbg_crypt() for ENCRYPT path In sev_dbg_crypt(), the per-iteration transfer length is bounded by the source page offset (PAGE_SIZE - s_off) but not by the destination page off | |
| CVE-2026-53399 | Cri | 9.8 | < 5.14.0-687.44.1.el9_8 | 5.14.0-687.44.1.el9_8 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: nfsd: release layout stid on setlease failure nfs4_alloc_stid() publishes the new stid into cl->cl_stateids via idr_alloc_cyclic() under cl_lock before returning to nfsd4_alloc_layout_stateid(). When nfsd4_layo | |
| CVE-2026-53398 | Cri | 9.8 | < 5.14.0-687.56.1.el9_8 | 5.14.0-687.56.1.el9_8 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: NFSD: Fix SECINFO_NO_NAME decode error cleanup nfsd4_decode_secinfo_no_name() currently initializes sin_exp after decoding sin_style. If the XDR stream is truncated, the decoder returns nfserr_bad_xdr before si | |
| CVE-2026-53397 | Hig | 7.5 | < 5.14.0-687.44.1.el9_8 | 5.14.0-687.44.1.el9_8 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: nfsd: fix posix_acl leak on SETACL decode failure nfsaclsvc_decode_setaclargs() and nfs3svc_decode_setaclargs() each call nfs_stream_decode_acl() twice, first for NFS_ACL and then for NFS_DFACL. Each successfu | |
| CVE-2026-53395 | Hig | 7.5 | < 6.12.0-264.9.1.el10_3 | 6.12.0-264.9.1.el10_3 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: nfsd: fix dead ACL conflict guard in nfsd4_create nfsd4_create() steals create->cr_dpacl/cr_pacl into the local nfsd_attrs via the designated initializer, then immediately sets the source pointers to NULL. The | |
| CVE-2026-53392 | Hig | 7.5 | < 5.14.0-687.44.1.el9_8 | 5.14.0-687.44.1.el9_8 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: NFSv4/flexfiles: reject zero filehandle version count ff_layout_alloc_lseg() decodes the filehandle-version array count from the flexfiles layout body. The value is used as the count for kzalloc_objs(), and the | |
| CVE-2026-53391 | Hig | 7.5 | < 5.14.0-687.44.1.el9_8 | 5.14.0-687.44.1.el9_8 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr nfs4_decode_mp_ds_addr() decodes the r_netid and r_addr opaques of a netaddr4 from a GETDEVICEINFO multipath-DS body, then immediately calls strrc | |
| CVE-2026-53388 | Hig | 7.8 | < 5.14.0-687.61.1.el9_8 | 5.14.0-687.61.1.el9_8 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before replacing page cache folio fuse_try_move_folio() unlocks the request on entry but does not re-lock it on the success path. This means fuse_chan_abort() can end the request and free | |
| CVE-2026-53374 | Hig | 8.8 | < 5.14.0-687.41.1.el9_8 | 5.14.0-687.41.1.el9_8 | Jul 19, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after unmapping but not after mapping. Since amdgpu_bo_create_kernel() does not zero-initialize the buffer, when a single PTE is written | |
| CVE-2026-53366 | Hig | 7.8 | < 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 | Jul 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: ipv4: account for fraggap on the paged allocation path In __ip_append_data(), when the paged-allocation branch is taken, alloclen and pagedlen are computed as alloclen = fragheaderlen + transhdrlen; pagedlen | |
| CVE-2026-53365 | Med | 5.5 | < 5.14.0-687.56.1.el9_8 | 5.14.0-687.56.1.el9_8 | Jul 13, 2026 | In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: fix zerocopy completion for multi-skb sends When a large message is fragmented into multiple skbs, the zerocopy uarg is only allocated and attached to the last skb in the loop. Non-final skbs carr | |
| CVE-2026-53361 | Hig | 7.1 | < 6.12.0-211.47.1.el10_2 | 6.12.0-211.47.1.el10_2 | Jul 4, 2026 | In the Linux kernel, the following vulnerability has been resolved: af_unix: Set gc_in_progress to true in unix_gc(). Igor Ushakov reported that unix_gc() could run with gc_in_progress being false if the work is scheduled while running: Thread 1 Thread 2 | |
| CVE-2026-53360 | Hig | 8.8 | < 5.14.0-687.56.1.el9_8 | 5.14.0-687.56.1.el9_8 | Jul 4, 2026 | In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use As per the GHCB spec, when using GHCB v2+ require the software scratch area to reside in the GHCB's shared buffer. Note, things like Page State Chan | |
| CVE-2026-53359 | Hig | 8.8 | < 5.14.0-687.24.1.el9_8 | 5.14.0-687.24.1.el9_8 | Jul 4, 2026 | In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Fix shadow paging use-after-free due to unexpected role Commit 0cb2af2ea66ad ("KVM: x86: Fix shadow paging use-after-free due to unexpected GFN") fixed a shadow paging mismatch between stored and comp | |
| CVE-2026-53357 | Hig | 8.0 | < 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 | Jul 2, 2026 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del() bt_accept_dequeue() unlinks a not-yet-accepted child from the parent accept queue and release_sock()s it before returning, so the returned s |
- affected < 5.14.0-687.50.1.el9_8fixed 5.14.0-687.50.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: keys: Pin request_key_auth payload in instantiate paths A: request_key() B: KEYCTL_INSTANTIATE_IOV ================ ========================= create auth key store rka in auth key wait for helper
- affected < 5.14.0-687.44.1.el9_8fixed 5.14.0-687.44.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: exfat: fix potential use-after-free in exfat_find_dir_entry() In exfat_find_dir_entry(), the buffer_head obtained from exfat_get_dentry() is released with brelse(bh) before the fall-through TYPE_EXTEND branch r
- affected < 5.14.0-687.51.1.el9_8fixed 5.14.0-687.51.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix UAF in __blkcg_rstat_flush() When multiple blkgs in the same blkcg are released concurrently, a use-after-free can occur. The race happens when one blkg's __blkcg_rstat_flush() removes another b
- affected < 5.14.0-687.47.1.el9_8fixed 5.14.0-687.47.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done tipc_aead_decrypt() goes straight from tipc_bearer_hold(b) to crypto_aead_decrypt(req) without taking a reference on the netns, unlike the encrypt pa
- affected < 5.14.0-687.44.1.el9_8fixed 5.14.0-687.44.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: pNFS: Fix use-after-free in pnfs_update_layout() When hitting the NFS_LAYOUT_RETURN branch in pnfs_update_layout(), the code calls pnfs_prepare_to_retry_layoutget(lo). If it succeeds, pnfs_put_layout_hdr(lo) is
- affected < 5.14.0-687.54.1.el9_8fixed 5.14.0-687.54.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Fix page overflow in sev_dbg_crypt() for ENCRYPT path In sev_dbg_crypt(), the per-iteration transfer length is bounded by the source page offset (PAGE_SIZE - s_off) but not by the destination page off
- affected < 5.14.0-687.44.1.el9_8fixed 5.14.0-687.44.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: nfsd: release layout stid on setlease failure nfs4_alloc_stid() publishes the new stid into cl->cl_stateids via idr_alloc_cyclic() under cl_lock before returning to nfsd4_alloc_layout_stateid(). When nfsd4_layo
- affected < 5.14.0-687.56.1.el9_8fixed 5.14.0-687.56.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: NFSD: Fix SECINFO_NO_NAME decode error cleanup nfsd4_decode_secinfo_no_name() currently initializes sin_exp after decoding sin_style. If the XDR stream is truncated, the decoder returns nfserr_bad_xdr before si
- affected < 5.14.0-687.44.1.el9_8fixed 5.14.0-687.44.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix posix_acl leak on SETACL decode failure nfsaclsvc_decode_setaclargs() and nfs3svc_decode_setaclargs() each call nfs_stream_decode_acl() twice, first for NFS_ACL and then for NFS_DFACL. Each successfu
- affected < 6.12.0-264.9.1.el10_3fixed 6.12.0-264.9.1.el10_3
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix dead ACL conflict guard in nfsd4_create nfsd4_create() steals create->cr_dpacl/cr_pacl into the local nfsd_attrs via the designated initializer, then immediately sets the source pointers to NULL. The
- affected < 5.14.0-687.44.1.el9_8fixed 5.14.0-687.44.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: NFSv4/flexfiles: reject zero filehandle version count ff_layout_alloc_lseg() decodes the filehandle-version array count from the flexfiles layout body. The value is used as the count for kzalloc_objs(), and the
- affected < 5.14.0-687.44.1.el9_8fixed 5.14.0-687.44.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr nfs4_decode_mp_ds_addr() decodes the r_netid and r_addr opaques of a netaddr4 from a GETDEVICEINFO multipath-DS body, then immediately calls strrc
- affected < 5.14.0-687.61.1.el9_8fixed 5.14.0-687.61.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before replacing page cache folio fuse_try_move_folio() unlocks the request on entry but does not re-lock it on the success path. This means fuse_chan_abort() can end the request and free
- affected < 5.14.0-687.41.1.el9_8fixed 5.14.0-687.41.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after unmapping but not after mapping. Since amdgpu_bo_create_kernel() does not zero-initialize the buffer, when a single PTE is written
- affected < 5.14.0-687.46.1.el9_8fixed 5.14.0-687.46.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: ipv4: account for fraggap on the paged allocation path In __ip_append_data(), when the paged-allocation branch is taken, alloclen and pagedlen are computed as alloclen = fragheaderlen + transhdrlen; pagedlen
- affected < 5.14.0-687.56.1.el9_8fixed 5.14.0-687.56.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: fix zerocopy completion for multi-skb sends When a large message is fragmented into multiple skbs, the zerocopy uarg is only allocated and attached to the last skb in the loop. Non-final skbs carr
- affected < 6.12.0-211.47.1.el10_2fixed 6.12.0-211.47.1.el10_2
In the Linux kernel, the following vulnerability has been resolved: af_unix: Set gc_in_progress to true in unix_gc(). Igor Ushakov reported that unix_gc() could run with gc_in_progress being false if the work is scheduled while running: Thread 1 Thread 2
- affected < 5.14.0-687.56.1.el9_8fixed 5.14.0-687.56.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use As per the GHCB spec, when using GHCB v2+ require the software scratch area to reside in the GHCB's shared buffer. Note, things like Page State Chan
- affected < 5.14.0-687.24.1.el9_8fixed 5.14.0-687.24.1.el9_8
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Fix shadow paging use-after-free due to unexpected role Commit 0cb2af2ea66ad ("KVM: x86: Fix shadow paging use-after-free due to unexpected GFN") fixed a shadow paging mismatch between stored and comp
- affected < 6.12.0-211.63.1.el10_2fixed 6.12.0-211.63.1.el10_2
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del() bt_accept_dequeue() unlinks a not-yet-accepted child from the parent accept queue and release_sock()s it before returning, so the returned s
Page 18 of 71