Описание
Important: kernel security, bug fix, and enhancement update
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
-
kernel: can: bcm: add locking for bcm_op runtime updates (CVE-2025-38004)
-
kernel: ipv6: add NULL checks for idev in SRv6 paths (CVE-2026-23442)
-
kernel: udp: Fix wildcard bind conflict check when using hash2 (CVE-2026-31503)
-
kernel: ipv6: prevent possible UaF in addrconf_permanent_addr() (CVE-2026-43339)
-
kernel: tcp: call sk_data_ready() after listener migration (CVE-2026-46015)
-
kernel: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (CVE-2026-46266)
-
kernel: flow_dissector: do not dissect PPPoE PFC frames (CVE-2026-46306)
-
kernel: io_uring/poll: fix signed comparison in io_poll_get_ownership() (CVE-2026-52933)
-
kernel: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (CVE-2026-53075)
-
kernel: KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation (CVE-2026-53277)
-
kernel: ipv6: sit: reload inner IPv6 header after GSO offloads (CVE-2026-53228)
-
kernel: net: add pskb_may_pull() to skb_gro_receive_list() (CVE-2026-53235)
-
kernel: net: guard timestamp cmsgs to real error queue skbs (CVE-2026-53223)
-
kernel: ipv6: mcast: Fix use-after-free when processing MLD queries (CVE-2026-53275)
-
kernel: ipv6: anycast: insert aca into global hash under idev->lock (CVE-2026-53259)
-
kernel: ipv4: free net->ipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table() (CVE-2026-64002)
-
kernel: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() (CVE-2026-63993)
-
kernel: fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req (CVE-2026-64265)
-
kernel: nvmet-auth: validate reply message payload bounds against transfer length (CVE-2026-64319)
-
kernel: KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU (CVE-2026-64287)
-
kernel: rhashtable: clear stale iter->p on table restart (CVE-2026-64563)
-
kernel: smb: client: fix double-free in SMB2_close() replay (CVE-2026-64597)
Bug Fix(es) and Enhancement(s):
- Customer needs "netfilter: nfnetlink_queue: optimize verdict lookup with hash table" patch [Rocky Linux 10.2] (JIRA:Rocky Linux-132852)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Затронутые продукты
Rocky Linux 10
Связанные CVE
Ссылки на источники
Исправления
- Red Hat - 2484456
- Red Hat - 2370992
- Red Hat - 2510892
- Red Hat - 2507041
- Red Hat - 2460736
- Red Hat - 2511932
- Red Hat - 2507096
- Red Hat - 2492745
- Red Hat - 2486463
- Red Hat - 2454807
- Red Hat - 2492295
- Red Hat - 2502363
- Red Hat - 2502369
- Red Hat - 2492841
- Red Hat - 2481936
- Red Hat - 2492725
- Red Hat - 2492733
- Red Hat - 2492097
- Red Hat - 2468102
- Red Hat - 2492850
Связанные уязвимости
In the Linux kernel, the following vulnerability has been resolved: can: bcm: add locking for bcm_op runtime updates The CAN broadcast manager (CAN BCM) can send a sequence of CAN frames via hrtimer. The content and also the length of the sequence can be changed resp reduced at runtime where the 'currframe' counter is then set to zero. Although this appeared to be a safe operation the updates of 'currframe' can be triggered from user space and hrtimer context in bcm_can_tx(). Anderson Nascimento created a proof of concept that triggered a KASAN slab-out-of-bounds read access which can be prevented with a spin_lock_bh. At the rework of bcm_can_tx() the 'count' variable has been moved into the protected section as this variable can be modified from both contexts too.
In the Linux kernel, the following vulnerability has been resolved: can: bcm: add locking for bcm_op runtime updates The CAN broadcast manager (CAN BCM) can send a sequence of CAN frames via hrtimer. The content and also the length of the sequence can be changed resp reduced at runtime where the 'currframe' counter is then set to zero. Although this appeared to be a safe operation the updates of 'currframe' can be triggered from user space and hrtimer context in bcm_can_tx(). Anderson Nascimento created a proof of concept that triggered a KASAN slab-out-of-bounds read access which can be prevented with a spin_lock_bh. At the rework of bcm_can_tx() the 'count' variable has been moved into the protected section as this variable can be modified from both contexts too.
In the Linux kernel, the following vulnerability has been resolved: can: bcm: add locking for bcm_op runtime updates The CAN broadcast manager (CAN BCM) can send a sequence of CAN frames via hrtimer. The content and also the length of the sequence can be changed resp reduced at runtime where the 'currframe' counter is then set to zero. Although this appeared to be a safe operation the updates of 'currframe' can be triggered from user space and hrtimer context in bcm_can_tx(). Anderson Nascimento created a proof of concept that triggered a KASAN slab-out-of-bounds read access which can be prevented with a spin_lock_bh. At the rework of bcm_can_tx() the 'count' variable has been moved into the protected section as this variable can be modified from both contexts too.
In the Linux kernel, the following vulnerability has been resolved: c ...