Описание
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: fbcon: Set fb_display[i]->mode to NULL when the mode is released (CVE-2025-40323)
-
kernel: libceph: fix potential use-after-free in have_mon_and_osd_map() (CVE-2025-68285)
-
kernel: libceph: make decode_pool() more resilient against corrupted osdmaps (CVE-2025-71116)
-
kernel: libceph: prevent potential out-of-bounds reads in handle_auth_done() (CVE-2026-22984)
-
kernel: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (CVE-2026-22990)
-
kernel: Linux kernel: Denial of Service in libceph OSD client due to unreset sparse-read state (CVE-2026-23136)
-
kernel: drm/amdgpu/vcn3: Prevent OOB reads when parsing dec msg (CVE-2026-46230)
-
kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing IB (CVE-2026-46204)
-
kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg (CVE-2026-46199)
-
kernel: drm/amdgpu/userq: fix access to stale wptr mapping (CVE-2026-46311)
-
kernel: af_unix: Drop all SCM attributes for SOCKMAP (CVE-2026-53005)
-
kernel: accel/ivpu: Add buffer overflow check in MS get_info_ioctl (CVE-2026-53203)
-
kernel: drm/xe/eustall: Fix drm_dev_put called before stream disable in close (CVE-2026-53290)
-
kernel: drm/virtio: use uninterruptible resv lock for plane updates (CVE-2026-64098)
-
kernel: Linux kernel: PPPoE memory corruption via stale pointer (CVE-2026-68121)
-
kernel: drm/amdgpu/vce: fix integer overflow in image size (CVE-2026-68108)
-
kernel: drm/amdkfd: fix 32-bit overflow in CWSR total size calculation (CVE-2026-68257)
-
kernel: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists (CVE-2026-68267)
-
kernel: drm/xe: Hold a dma-buf reference for imported BOs (CVE-2026-68266)
-
kernel: drm/amdgpu: Fix context pstate override handling (CVE-2026-68273)
-
kernel: Linux kernel IPVS: Denial of Service due to stale memory references (CVE-2026-80714)
-
kernel: nvme-tcp: fix host memory disclosure on R2T for a read command (CVE-2026-89481)
Bug Fix(es) and Enhancement(s):
- Bypass DMA APIs for coherent allocations for pre-mapped memory [rhel-10.2.z] (JIRA:Rocky Linux-252331)
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 - 2419883
- Red Hat - 2422801
- Red Hat - 2429602
- Red Hat - 2432389
- Red Hat - 2432400
- Red Hat - 2439852
- Red Hat - 2482533
- Red Hat - 2482543
- Red Hat - 2482649
- Red Hat - 2486470
- Red Hat - 2492381
- Red Hat - 2492798
- Red Hat - 2493739
- Red Hat - 2502536
- Red Hat - 2513233
- Red Hat - 2513361
- Red Hat - 2513372
- Red Hat - 2513414
- Red Hat - 2513429
- Red Hat - 2513434
Связанные уязвимости
ELSA-2026-71602: kernel security, bug fix, and enhancement update (IMPORTANT)
In the Linux kernel, the following vulnerability has been resolved: fbcon: Set fb_display[i]->mode to NULL when the mode is released Recently, we discovered the following issue through syzkaller: BUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0 Read of size 4 at addr ff11000001b3c69c by task syz.xxx ... Call Trace: <TASK> dump_stack_lvl+0xab/0xe0 print_address_description.constprop.0+0x2c/0x390 print_report+0xb9/0x280 kasan_report+0xb8/0xf0 fb_mode_is_equal+0x285/0x2f0 fbcon_mode_deleted+0x129/0x180 fb_set_var+0xe7f/0x11d0 do_fb_ioctl+0x6a0/0x750 fb_ioctl+0xe0/0x140 __x64_sys_ioctl+0x193/0x210 do_syscall_64+0x5f/0x9c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e Based on experimentation and analysis, during framebuffer unregistration, only the memory of fb_info->modelist is freed, without setting the corresponding fb_display[i]->mode to NULL for the freed modes. This leads to UAF issues during subsequent accesses. Here's an example of reproduction steps: 1. With /dev/fb0 ...
In the Linux kernel, the following vulnerability has been resolved: fbcon: Set fb_display[i]->mode to NULL when the mode is released Recently, we discovered the following issue through syzkaller: BUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0 Read of size 4 at addr ff11000001b3c69c by task syz.xxx ... Call Trace: <TASK> dump_stack_lvl+0xab/0xe0 print_address_description.constprop.0+0x2c/0x390 print_report+0xb9/0x280 kasan_report+0xb8/0xf0 fb_mode_is_equal+0x285/0x2f0 fbcon_mode_deleted+0x129/0x180 fb_set_var+0xe7f/0x11d0 do_fb_ioctl+0x6a0/0x750 fb_ioctl+0xe0/0x140 __x64_sys_ioctl+0x193/0x210 do_syscall_64+0x5f/0x9c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e Based on experimentation and analysis, during framebuffer unregistration, only the memory of fb_info->modelist is freed, without setting the corresponding fb_display[i]->mode to NULL for the freed modes. This leads to UAF issues during subsequent accesses. Here's an example of reproduction steps: 1. With /dev/fb0 ...
In the Linux kernel, the following vulnerability has been resolved: fbcon: Set fb_display[i]->mode to NULL when the mode is released Recently, we discovered the following issue through syzkaller: BUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0 Read of size 4 at addr ff11000001b3c69c by task syz.xxx ... Call Trace: <TASK> dump_stack_lvl+0xab/0xe0 print_address_description.constprop.0+0x2c/0x390 print_report+0xb9/0x280 kasan_report+0xb8/0xf0 fb_mode_is_equal+0x285/0x2f0 fbcon_mode_deleted+0x129/0x180 fb_set_var+0xe7f/0x11d0 do_fb_ioctl+0x6a0/0x750 fb_ioctl+0xe0/0x140 __x64_sys_ioctl+0x193/0x210 do_syscall_64+0x5f/0x9c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e Based on experimentation and analysis, during framebuffer unregistration, only the memory of fb_info->modelist is freed, without setting the corresponding fb_display[i]->mode to NULL for the freed modes. This leads to UAF issues during subsequent accesses. Here's an example of reproduction steps: 1.
fbcon: Set fb_display[i]->mode to NULL when the mode is released