Security update for the Linux Kernel SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2024:4345-1 Final 1 1 2024-12-17T08:31:01Z current 2024-12-17T08:31:01Z 2024-12-17T08:31:01Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for the Linux Kernel The SUSE Linux Enterprise 15 SP4 RT kernel was updated to receive various security bugfixes. The following security bugs were fixed: - CVE-2024-26782: mptcp: fix double-free on socket dismantle (bsc#1222590). - CVE-2024-43854: Initialize integrity buffer to zero before writing it to media (bsc#1229345) - CVE-2024-44932: idpf: fix UAFs when destroying the queues (bsc#1229808). - CVE-2024-44964: idpf: fix memory leaks and crashes while performing a soft reset (bsc#1230220). - CVE-2024-47757: nilfs2: fix potential oob read in nilfs_btree_check_delete() (bsc#1232187). - CVE-2024-49925: fbdev: efifb: Register sysfs groups through driver core (bsc#1232224) - CVE-2024-49945: net/ncsi: Disable the ncsi work before freeing the associated structure (bsc#1232165). - CVE-2024-50089: unicode: Do not special case ignorable code points (bsc#1232860). - CVE-2024-50115: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory (bsc#1232919). - CVE-2024-50125: Bluetooth: SCO: Fix UAF on sco_sock_timeout (bsc#1232928). - CVE-2024-50127: net: sched: fix use-after-free in taprio_change() (bsc#1232907). - CVE-2024-50154: tcp/dccp: Do not use timer_pending() in reqsk_queue_unlink() (bsc#1233070). - CVE-2024-50205: ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size() (bsc#1233293). - CVE-2024-50208: RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages (bsc#1233117). - CVE-2024-50259: netdevsim: Add trailing zero to terminate the string in nsim_nexthop_bucket_activity_write() (bsc#1233214). - CVE-2024-50264: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans (bsc#1233453). - CVE-2024-50267: usb: serial: io_edgeport: fix use after free in debug printk (bsc#1233456). - CVE-2024-50274: idpf: avoid vport access in idpf_get_link_ksettings (bsc#1233463). - CVE-2024-50279: dm cache: fix out-of-bounds access to the dirty bitset when resizing (bsc#1233468). - CVE-2024-50290: media: cx24116: prevent overflows on SNR calculus (bsc#1233479). - CVE-2024-50301: security/keys: fix slab-out-of-bounds in key_task_permission (bsc#1233490). - CVE-2024-50302: HID: core: zero-initialize the report buffer (bsc#1233491). - CVE-2024-53061: media: s5p-jpeg: prevent buffer overflows (bsc#1233555). - CVE-2024-53063: media: dvbdev: prevent the risk of out of memory access (bsc#1233557). - CVE-2024-53068: firmware: arm_scmi: Fix slab-use-after-free in scmi_bus_notifier() (bsc#1233561). The following non-security bugs were fixed: - Update config files (bsc#1218644). - Update config files. Enabled IDPF for ARM64 (bsc#1221309) - initramfs: avoid filename buffer overrun (bsc#1232436). - kernel-binary: Enable livepatch package only when livepatch is enabled Otherwise the filelist may be empty failing the build (bsc#1218644). - mm/memory: add non-anonymous page check in the copy_present_page() (bsc#1231646). - rpm/scripts: Remove obsolete Symbols.list Symbols.list is not longer needed by the new klp-convert implementation. (bsc#1218644) - x86/kexec: Add EFI config table identity mapping for kexec kernel (bsc#1220382). - x86/mm/ident_map: Use gbpages only where full GB page should be mapped (bsc#1220382). The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-2024-4345,SUSE-SLE-Micro-5.3-2024-4345,SUSE-SLE-Micro-5.4-2024-4345 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ Link for SUSE-SU-2024:4345-1 https://lists.suse.com/pipermail/sle-security-updates/2024-December/020018.html E-Mail link for SUSE-SU-2024:4345-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1218644 SUSE Bug 1218644 https://bugzilla.suse.com/1220382 SUSE Bug 1220382 https://bugzilla.suse.com/1221309 SUSE Bug 1221309 https://bugzilla.suse.com/1222590 SUSE Bug 1222590 https://bugzilla.suse.com/1229345 SUSE Bug 1229345 https://bugzilla.suse.com/1229808 SUSE Bug 1229808 https://bugzilla.suse.com/1230220 SUSE Bug 1230220 https://bugzilla.suse.com/1231646 SUSE Bug 1231646 https://bugzilla.suse.com/1232165 SUSE Bug 1232165 https://bugzilla.suse.com/1232187 SUSE Bug 1232187 https://bugzilla.suse.com/1232224 SUSE Bug 1232224 https://bugzilla.suse.com/1232312 SUSE Bug 1232312 https://bugzilla.suse.com/1232436 SUSE Bug 1232436 https://bugzilla.suse.com/1232860 SUSE Bug 1232860 https://bugzilla.suse.com/1232907 SUSE Bug 1232907 https://bugzilla.suse.com/1232919 SUSE Bug 1232919 https://bugzilla.suse.com/1232928 SUSE Bug 1232928 https://bugzilla.suse.com/1233070 SUSE Bug 1233070 https://bugzilla.suse.com/1233117 SUSE Bug 1233117 https://bugzilla.suse.com/1233214 SUSE Bug 1233214 https://bugzilla.suse.com/1233293 SUSE Bug 1233293 https://bugzilla.suse.com/1233453 SUSE Bug 1233453 https://bugzilla.suse.com/1233456 SUSE Bug 1233456 https://bugzilla.suse.com/1233463 SUSE Bug 1233463 https://bugzilla.suse.com/1233468 SUSE Bug 1233468 https://bugzilla.suse.com/1233479 SUSE Bug 1233479 https://bugzilla.suse.com/1233490 SUSE Bug 1233490 https://bugzilla.suse.com/1233491 SUSE Bug 1233491 https://bugzilla.suse.com/1233555 SUSE Bug 1233555 https://bugzilla.suse.com/1233557 SUSE Bug 1233557 https://bugzilla.suse.com/1233561 SUSE Bug 1233561 https://bugzilla.suse.com/1233977 SUSE Bug 1233977 https://www.suse.com/security/cve/CVE-2023-52922/ SUSE CVE CVE-2023-52922 page https://www.suse.com/security/cve/CVE-2024-26782/ SUSE CVE CVE-2024-26782 page https://www.suse.com/security/cve/CVE-2024-43854/ SUSE CVE CVE-2024-43854 page https://www.suse.com/security/cve/CVE-2024-44932/ SUSE CVE CVE-2024-44932 page https://www.suse.com/security/cve/CVE-2024-44964/ SUSE CVE CVE-2024-44964 page https://www.suse.com/security/cve/CVE-2024-47757/ SUSE CVE CVE-2024-47757 page https://www.suse.com/security/cve/CVE-2024-49925/ SUSE CVE CVE-2024-49925 page https://www.suse.com/security/cve/CVE-2024-49945/ SUSE CVE CVE-2024-49945 page https://www.suse.com/security/cve/CVE-2024-50017/ SUSE CVE CVE-2024-50017 page https://www.suse.com/security/cve/CVE-2024-50089/ SUSE CVE CVE-2024-50089 page https://www.suse.com/security/cve/CVE-2024-50115/ SUSE CVE CVE-2024-50115 page https://www.suse.com/security/cve/CVE-2024-50125/ SUSE CVE CVE-2024-50125 page https://www.suse.com/security/cve/CVE-2024-50127/ SUSE CVE CVE-2024-50127 page https://www.suse.com/security/cve/CVE-2024-50154/ SUSE CVE CVE-2024-50154 page https://www.suse.com/security/cve/CVE-2024-50205/ SUSE CVE CVE-2024-50205 page https://www.suse.com/security/cve/CVE-2024-50208/ SUSE CVE CVE-2024-50208 page https://www.suse.com/security/cve/CVE-2024-50259/ SUSE CVE CVE-2024-50259 page https://www.suse.com/security/cve/CVE-2024-50264/ SUSE CVE CVE-2024-50264 page https://www.suse.com/security/cve/CVE-2024-50267/ SUSE CVE CVE-2024-50267 page https://www.suse.com/security/cve/CVE-2024-50274/ SUSE CVE CVE-2024-50274 page https://www.suse.com/security/cve/CVE-2024-50279/ SUSE CVE CVE-2024-50279 page https://www.suse.com/security/cve/CVE-2024-50290/ SUSE CVE CVE-2024-50290 page https://www.suse.com/security/cve/CVE-2024-50301/ SUSE CVE CVE-2024-50301 page https://www.suse.com/security/cve/CVE-2024-50302/ SUSE CVE CVE-2024-50302 page https://www.suse.com/security/cve/CVE-2024-53061/ SUSE CVE CVE-2024-53061 page https://www.suse.com/security/cve/CVE-2024-53063/ SUSE CVE CVE-2024-53063 page https://www.suse.com/security/cve/CVE-2024-53068/ SUSE CVE CVE-2024-53068 page SUSE Linux Enterprise Micro 5.3 SUSE Linux Enterprise Micro 5.4 cluster-md-kmp-rt-5.14.21-150400.15.103.1 dlm-kmp-rt-5.14.21-150400.15.103.1 gfs2-kmp-rt-5.14.21-150400.15.103.1 kernel-devel-rt-5.14.21-150400.15.103.1 kernel-rt-5.14.21-150400.15.103.1 kernel-rt-devel-5.14.21-150400.15.103.1 kernel-rt-extra-5.14.21-150400.15.103.1 kernel-rt-livepatch-5.14.21-150400.15.103.1 kernel-rt-livepatch-devel-5.14.21-150400.15.103.1 kernel-rt-optional-5.14.21-150400.15.103.1 kernel-rt_debug-5.14.21-150400.15.103.1 kernel-rt_debug-devel-5.14.21-150400.15.103.1 kernel-source-rt-5.14.21-150400.15.103.1 kernel-syms-rt-5.14.21-150400.15.103.1 kselftests-kmp-rt-5.14.21-150400.15.103.1 ocfs2-kmp-rt-5.14.21-150400.15.103.1 reiserfs-kmp-rt-5.14.21-150400.15.103.1 kernel-rt-5.14.21-150400.15.103.1 as a component of SUSE Linux Enterprise Micro 5.3 kernel-source-rt-5.14.21-150400.15.103.1 as a component of SUSE Linux Enterprise Micro 5.3 kernel-rt-5.14.21-150400.15.103.1 as a component of SUSE Linux Enterprise Micro 5.4 kernel-source-rt-5.14.21-150400.15.103.1 as a component of SUSE Linux Enterprise Micro 5.4 In the Linux kernel, the following vulnerability has been resolved: can: bcm: Fix UAF in bcm_proc_show() BUG: KASAN: slab-use-after-free in bcm_proc_show+0x969/0xa80 Read of size 8 at addr ffff888155846230 by task cat/7862 CPU: 1 PID: 7862 Comm: cat Not tainted 6.5.0-rc1-00153-gc8746099c197 #230 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0xd5/0x150 print_report+0xc1/0x5e0 kasan_report+0xba/0xf0 bcm_proc_show+0x969/0xa80 seq_read_iter+0x4f6/0x1260 seq_read+0x165/0x210 proc_reg_read+0x227/0x300 vfs_read+0x1d5/0x8d0 ksys_read+0x11e/0x240 do_syscall_64+0x35/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd Allocated by task 7846: kasan_save_stack+0x1e/0x40 kasan_set_track+0x21/0x30 __kasan_kmalloc+0x9e/0xa0 bcm_sendmsg+0x264b/0x44e0 sock_sendmsg+0xda/0x180 ____sys_sendmsg+0x735/0x920 ___sys_sendmsg+0x11d/0x1b0 __sys_sendmsg+0xfa/0x1d0 do_syscall_64+0x35/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd Freed by task 7846: kasan_save_stack+0x1e/0x40 kasan_set_track+0x21/0x30 kasan_save_free_info+0x27/0x40 ____kasan_slab_free+0x161/0x1c0 slab_free_freelist_hook+0x119/0x220 __kmem_cache_free+0xb4/0x2e0 rcu_core+0x809/0x1bd0 bcm_op is freed before procfs entry be removed in bcm_release(), this lead to bcm_proc_show() may read the freed bcm_op. CVE-2023-52922 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2023-52922.html CVE-2023-52922 https://bugzilla.suse.com/1233977 SUSE Bug 1233977 In the Linux kernel, the following vulnerability has been resolved: mptcp: fix double-free on socket dismantle when MPTCP server accepts an incoming connection, it clones its listener socket. However, the pointer to 'inet_opt' for the new socket has the same value as the original one: as a consequence, on program exit it's possible to observe the following splat: BUG: KASAN: double-free in inet_sock_destruct+0x54f/0x8b0 Free of addr ffff888485950880 by task swapper/25/0 CPU: 25 PID: 0 Comm: swapper/25 Kdump: loaded Not tainted 6.8.0-rc1+ #609 Hardware name: Supermicro SYS-6027R-72RF/X9DRH-7TF/7F/iTF/iF, BIOS 3.0 07/26/2013 Call Trace: <IRQ> dump_stack_lvl+0x32/0x50 print_report+0xca/0x620 kasan_report_invalid_free+0x64/0x90 __kasan_slab_free+0x1aa/0x1f0 kfree+0xed/0x2e0 inet_sock_destruct+0x54f/0x8b0 __sk_destruct+0x48/0x5b0 rcu_do_batch+0x34e/0xd90 rcu_core+0x559/0xac0 __do_softirq+0x183/0x5a4 irq_exit_rcu+0x12d/0x170 sysvec_apic_timer_interrupt+0x6b/0x80 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x16/0x20 RIP: 0010:cpuidle_enter_state+0x175/0x300 Code: 30 00 0f 84 1f 01 00 00 83 e8 01 83 f8 ff 75 e5 48 83 c4 18 44 89 e8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc fb 45 85 ed <0f> 89 60 ff ff ff 48 c1 e5 06 48 c7 43 18 00 00 00 00 48 83 44 2b RSP: 0018:ffff888481cf7d90 EFLAGS: 00000202 RAX: 0000000000000000 RBX: ffff88887facddc8 RCX: 0000000000000000 RDX: 1ffff1110ff588b1 RSI: 0000000000000019 RDI: ffff88887fac4588 RBP: 0000000000000004 R08: 0000000000000002 R09: 0000000000043080 R10: 0009b02ea273363f R11: ffff88887fabf42b R12: ffffffff932592e0 R13: 0000000000000004 R14: 0000000000000000 R15: 00000022c880ec80 cpuidle_enter+0x4a/0xa0 do_idle+0x310/0x410 cpu_startup_entry+0x51/0x60 start_secondary+0x211/0x270 secondary_startup_64_no_verify+0x184/0x18b </TASK> Allocated by task 6853: kasan_save_stack+0x1c/0x40 kasan_save_track+0x10/0x30 __kasan_kmalloc+0xa6/0xb0 __kmalloc+0x1eb/0x450 cipso_v4_sock_setattr+0x96/0x360 netlbl_sock_setattr+0x132/0x1f0 selinux_netlbl_socket_post_create+0x6c/0x110 selinux_socket_post_create+0x37b/0x7f0 security_socket_post_create+0x63/0xb0 __sock_create+0x305/0x450 __sys_socket_create.part.23+0xbd/0x130 __sys_socket+0x37/0xb0 __x64_sys_socket+0x6f/0xb0 do_syscall_64+0x83/0x160 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Freed by task 6858: kasan_save_stack+0x1c/0x40 kasan_save_track+0x10/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x12c/0x1f0 kfree+0xed/0x2e0 inet_sock_destruct+0x54f/0x8b0 __sk_destruct+0x48/0x5b0 subflow_ulp_release+0x1f0/0x250 tcp_cleanup_ulp+0x6e/0x110 tcp_v4_destroy_sock+0x5a/0x3a0 inet_csk_destroy_sock+0x135/0x390 tcp_fin+0x416/0x5c0 tcp_data_queue+0x1bc8/0x4310 tcp_rcv_state_process+0x15a3/0x47b0 tcp_v4_do_rcv+0x2c1/0x990 tcp_v4_rcv+0x41fb/0x5ed0 ip_protocol_deliver_rcu+0x6d/0x9f0 ip_local_deliver_finish+0x278/0x360 ip_local_deliver+0x182/0x2c0 ip_rcv+0xb5/0x1c0 __netif_receive_skb_one_core+0x16e/0x1b0 process_backlog+0x1e3/0x650 __napi_poll+0xa6/0x500 net_rx_action+0x740/0xbb0 __do_softirq+0x183/0x5a4 The buggy address belongs to the object at ffff888485950880 which belongs to the cache kmalloc-64 of size 64 The buggy address is located 0 bytes inside of 64-byte region [ffff888485950880, ffff8884859508c0) The buggy address belongs to the physical page: page:0000000056d1e95e refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888485950700 pfn:0x485950 flags: 0x57ffffc0000800(slab|node=1|zone=2|lastcpupid=0x1fffff) page_type: 0xffffffff() raw: 0057ffffc0000800 ffff88810004c640 ffffea00121b8ac0 dead000000000006 raw: ffff888485950700 0000000000200019 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff888485950780: fa fb fb ---truncated--- CVE-2024-26782 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-26782.html CVE-2024-26782 https://bugzilla.suse.com/1222590 SUSE Bug 1222590 In the Linux kernel, the following vulnerability has been resolved: block: initialize integrity buffer to zero before writing it to media Metadata added by bio_integrity_prep is using plain kmalloc, which leads to random kernel memory being written media. For PI metadata this is limited to the app tag that isn't used by kernel generated metadata, but for non-PI metadata the entire buffer leaks kernel memory. Fix this by adding the __GFP_ZERO flag to allocations for writes. CVE-2024-43854 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-43854.html CVE-2024-43854 https://bugzilla.suse.com/1229345 SUSE Bug 1229345 In the Linux kernel, the following vulnerability has been resolved: idpf: fix UAFs when destroying the queues The second tagged commit started sometimes (very rarely, but possible) throwing WARNs from net/core/page_pool.c:page_pool_disable_direct_recycling(). Turned out idpf frees interrupt vectors with embedded NAPIs *before* freeing the queues making page_pools' NAPI pointers lead to freed memory before these pools are destroyed by libeth. It's not clear whether there are other accesses to the freed vectors when destroying the queues, but anyway, we usually free queue/interrupt vectors only when the queues are destroyed and the NAPIs are guaranteed to not be referenced anywhere. Invert the allocation and freeing logic making queue/interrupt vectors be allocated first and freed last. Vectors don't require queues to be present, so this is safe. Additionally, this change allows to remove that useless queue->q_vector pointer cleanup, as vectors are still valid when freeing the queues (+ both are freed within one function, so it's not clear why nullify the pointers at all). CVE-2024-44932 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-44932.html CVE-2024-44932 https://bugzilla.suse.com/1229808 SUSE Bug 1229808 In the Linux kernel, the following vulnerability has been resolved: idpf: fix memory leaks and crashes while performing a soft reset The second tagged commit introduced a UAF, as it removed restoring q_vector->vport pointers after reinitializating the structures. This is due to that all queue allocation functions are performed here with the new temporary vport structure and those functions rewrite the backpointers to the vport. Then, this new struct is freed and the pointers start leading to nowhere. But generally speaking, the current logic is very fragile. It claims to be more reliable when the system is low on memory, but in fact, it consumes two times more memory as at the moment of running this function, there are two vports allocated with their queues and vectors. Moreover, it claims to prevent the driver from running into "bad state", but in fact, any error during the rebuild leaves the old vport in the partially allocated state. Finally, if the interface is down when the function is called, it always allocates a new queue set, but when the user decides to enable the interface later on, vport_open() allocates them once again, IOW there's a clear memory leak here. Just don't allocate a new queue set when performing a reset, that solves crashes and memory leaks. Readd the old queue number and reopen the interface on rollback - that solves limbo states when the device is left disabled and/or without HW queues enabled. CVE-2024-44964 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-44964.html CVE-2024-44964 https://bugzilla.suse.com/1230220 SUSE Bug 1230220 In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential oob read in nilfs_btree_check_delete() The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory access outside the block buffer when retrieving the maximum key if the root node has no entries. This does not usually happen because b-tree mappings with 0 child nodes are never created by mkfs.nilfs2 or nilfs2 itself. However, it can happen if the b-tree root node read from a device is configured that way, so fix this potential issue by adding a check for that case. CVE-2024-47757 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-47757.html CVE-2024-47757 https://bugzilla.suse.com/1232187 SUSE Bug 1232187 https://bugzilla.suse.com/1232188 SUSE Bug 1232188 In the Linux kernel, the following vulnerability has been resolved: fbdev: efifb: Register sysfs groups through driver core The driver core can register and cleanup sysfs groups already. Make use of that functionality to simplify the error handling and cleanup. Also avoid a UAF race during unregistering where the sysctl attributes were usable after the info struct was freed. CVE-2024-49925 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-49925.html CVE-2024-49925 https://bugzilla.suse.com/1232224 SUSE Bug 1232224 https://bugzilla.suse.com/1232225 SUSE Bug 1232225 In the Linux kernel, the following vulnerability has been resolved: net/ncsi: Disable the ncsi work before freeing the associated structure The work function can run after the ncsi device is freed, resulting in use-after-free bugs or kernel panic. CVE-2024-49945 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-49945.html CVE-2024-49945 https://bugzilla.suse.com/1232165 SUSE Bug 1232165 In the Linux kernel, the following vulnerability has been resolved: x86/mm/ident_map: Use gbpages only where full GB page should be mapped. When ident_pud_init() uses only GB pages to create identity maps, large ranges of addresses not actually requested can be included in the resulting table; a 4K request will map a full GB. This can include a lot of extra address space past that requested, including areas marked reserved by the BIOS. That allows processor speculation into reserved regions, that on UV systems can cause system halts. Only use GB pages when map creation requests include the full GB page of space. Fall back to using smaller 2M pages when only portions of a GB page are included in the request. No attempt is made to coalesce mapping requests. If a request requires a map entry at the 2M (pmd) level, subsequent mapping requests within the same 1G region will also be at the pmd level, even if adjacent or overlapping such requests could have been combined to map a full GB page. Existing usage starts with larger regions and then adds smaller regions, so this should not have any great consequence. CVE-2024-50017 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 moderate To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50017.html CVE-2024-50017 https://bugzilla.suse.com/1232312 SUSE Bug 1232312 ** REJECT ** This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. CVE-2024-50089 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50089.html CVE-2024-50089 https://bugzilla.suse.com/1232860 SUSE Bug 1232860 https://bugzilla.suse.com/1233250 SUSE Bug 1233250 In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory Ignore nCR3[4:0] when loading PDPTEs from memory for nested SVM, as bits 4:0 of CR3 are ignored when PAE paging is used, and thus VMRUN doesn't enforce 32-byte alignment of nCR3. In the absolute worst case scenario, failure to ignore bits 4:0 can result in an out-of-bounds read, e.g. if the target page is at the end of a memslot, and the VMM isn't using guard pages. Per the APM: The CR3 register points to the base address of the page-directory-pointer table. The page-directory-pointer table is aligned on a 32-byte boundary, with the low 5 address bits 4:0 assumed to be 0. And the SDM's much more explicit: 4:0 Ignored Note, KVM gets this right when loading PDPTRs, it's only the nSVM flow that is broken. CVE-2024-50115 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50115.html CVE-2024-50115 https://bugzilla.suse.com/1225742 SUSE Bug 1225742 https://bugzilla.suse.com/1232919 SUSE Bug 1232919 https://bugzilla.suse.com/1233019 SUSE Bug 1233019 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: Fix UAF on sco_sock_timeout conn->sk maybe have been unlinked/freed while waiting for sco_conn_lock so this checks if the conn->sk is still valid by checking if it part of sco_sk_list. CVE-2024-50125 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50125.html CVE-2024-50125 https://bugzilla.suse.com/1232928 SUSE Bug 1232928 https://bugzilla.suse.com/1232929 SUSE Bug 1232929 In the Linux kernel, the following vulnerability has been resolved: net: sched: fix use-after-free in taprio_change() In 'taprio_change()', 'admin' pointer may become dangling due to sched switch / removal caused by 'advance_sched()', and critical section protected by 'q->current_entry_lock' is too small to prevent from such a scenario (which causes use-after-free detected by KASAN). Fix this by prefer 'rcu_replace_pointer()' over 'rcu_assign_pointer()' to update 'admin' immediately before an attempt to schedule freeing. CVE-2024-50127 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50127.html CVE-2024-50127 https://bugzilla.suse.com/1232907 SUSE Bug 1232907 https://bugzilla.suse.com/1232908 SUSE Bug 1232908 In the Linux kernel, the following vulnerability has been resolved: tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). Martin KaFai Lau reported use-after-free [0] in reqsk_timer_handler(). """ We are seeing a use-after-free from a bpf prog attached to trace_tcp_retransmit_synack. The program passes the req->sk to the bpf_sk_storage_get_tracing kernel helper which does check for null before using it. """ The commit 83fccfc3940c ("inet: fix potential deadlock in reqsk_queue_unlink()") added timer_pending() in reqsk_queue_unlink() not to call del_timer_sync() from reqsk_timer_handler(), but it introduced a small race window. Before the timer is called, expire_timers() calls detach_timer(timer, true) to clear timer->entry.pprev and marks it as not pending. If reqsk_queue_unlink() checks timer_pending() just after expire_timers() calls detach_timer(), TCP will miss del_timer_sync(); the reqsk timer will continue running and send multiple SYN+ACKs until it expires. The reported UAF could happen if req->sk is close()d earlier than the timer expiration, which is 63s by default. The scenario would be 1. inet_csk_complete_hashdance() calls inet_csk_reqsk_queue_drop(), but del_timer_sync() is missed 2. reqsk timer is executed and scheduled again 3. req->sk is accept()ed and reqsk_put() decrements rsk_refcnt, but reqsk timer still has another one, and inet_csk_accept() does not clear req->sk for non-TFO sockets 4. sk is close()d 5. reqsk timer is executed again, and BPF touches req->sk Let's not use timer_pending() by passing the caller context to __inet_csk_reqsk_queue_drop(). Note that reqsk timer is pinned, so the issue does not happen in most use cases. [1] [0] BUG: KFENCE: use-after-free read in bpf_sk_storage_get_tracing+0x2e/0x1b0 Use-after-free read at 0x00000000a891fb3a (in kfence-#1): bpf_sk_storage_get_tracing+0x2e/0x1b0 bpf_prog_5ea3e95db6da0438_tcp_retransmit_synack+0x1d20/0x1dda bpf_trace_run2+0x4c/0xc0 tcp_rtx_synack+0xf9/0x100 reqsk_timer_handler+0xda/0x3d0 run_timer_softirq+0x292/0x8a0 irq_exit_rcu+0xf5/0x320 sysvec_apic_timer_interrupt+0x6d/0x80 asm_sysvec_apic_timer_interrupt+0x16/0x20 intel_idle_irq+0x5a/0xa0 cpuidle_enter_state+0x94/0x273 cpu_startup_entry+0x15e/0x260 start_secondary+0x8a/0x90 secondary_startup_64_no_verify+0xfa/0xfb kfence-#1: 0x00000000a72cc7b6-0x00000000d97616d9, size=2376, cache=TCPv6 allocated by task 0 on cpu 9 at 260507.901592s: sk_prot_alloc+0x35/0x140 sk_clone_lock+0x1f/0x3f0 inet_csk_clone_lock+0x15/0x160 tcp_create_openreq_child+0x1f/0x410 tcp_v6_syn_recv_sock+0x1da/0x700 tcp_check_req+0x1fb/0x510 tcp_v6_rcv+0x98b/0x1420 ipv6_list_rcv+0x2258/0x26e0 napi_complete_done+0x5b1/0x2990 mlx5e_napi_poll+0x2ae/0x8d0 net_rx_action+0x13e/0x590 irq_exit_rcu+0xf5/0x320 common_interrupt+0x80/0x90 asm_common_interrupt+0x22/0x40 cpuidle_enter_state+0xfb/0x273 cpu_startup_entry+0x15e/0x260 start_secondary+0x8a/0x90 secondary_startup_64_no_verify+0xfa/0xfb freed by task 0 on cpu 9 at 260507.927527s: rcu_core_si+0x4ff/0xf10 irq_exit_rcu+0xf5/0x320 sysvec_apic_timer_interrupt+0x6d/0x80 asm_sysvec_apic_timer_interrupt+0x16/0x20 cpuidle_enter_state+0xfb/0x273 cpu_startup_entry+0x15e/0x260 start_secondary+0x8a/0x90 secondary_startup_64_no_verify+0xfa/0xfb CVE-2024-50154 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50154.html CVE-2024-50154 https://bugzilla.suse.com/1233070 SUSE Bug 1233070 https://bugzilla.suse.com/1233072 SUSE Bug 1233072 In the Linux kernel, the following vulnerability has been resolved: ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size() The step variable is initialized to zero. It is changed in the loop, but if it's not changed it will remain zero. Add a variable check before the division. The observed behavior was introduced by commit 826b5de90c0b ("ALSA: firewire-lib: fix insufficient PCM rule for period/buffer size"), and it is difficult to show that any of the interval parameters will satisfy the snd_interval_test() condition with data from the amdtp_rate_table[] table. Found by Linux Verification Center (linuxtesting.org) with SVACE. CVE-2024-50205 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50205.html CVE-2024-50205 https://bugzilla.suse.com/1233293 SUSE Bug 1233293 https://bugzilla.suse.com/1233294 SUSE Bug 1233294 In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages Avoid memory corruption while setting up Level-2 PBL pages for the non MR resources when num_pages > 256K. There will be a single PDE page address (contiguous pages in the case of > PAGE_SIZE), but, current logic assumes multiple pages, leading to invalid memory access after 256K PBL entries in the PDE. CVE-2024-50208 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50208.html CVE-2024-50208 https://bugzilla.suse.com/1233117 SUSE Bug 1233117 https://bugzilla.suse.com/1233118 SUSE Bug 1233118 In the Linux kernel, the following vulnerability has been resolved: netdevsim: Add trailing zero to terminate the string in nsim_nexthop_bucket_activity_write() This was found by a static analyzer. We should not forget the trailing zero after copy_from_user() if we will further do some string operations, sscanf() in this case. Adding a trailing zero will ensure that the function performs properly. CVE-2024-50259 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50259.html CVE-2024-50259 https://bugzilla.suse.com/1233214 SUSE Bug 1233214 https://bugzilla.suse.com/1233215 SUSE Bug 1233215 In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans During loopback communication, a dangling pointer can be created in vsk->trans, potentially leading to a Use-After-Free condition. This issue is resolved by initializing vsk->trans to NULL. CVE-2024-50264 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50264.html CVE-2024-50264 https://bugzilla.suse.com/1233453 SUSE Bug 1233453 https://bugzilla.suse.com/1233712 SUSE Bug 1233712 In the Linux kernel, the following vulnerability has been resolved: USB: serial: io_edgeport: fix use after free in debug printk The "dev_dbg(&urb->dev->dev, ..." which happens after usb_free_urb(urb) is a use after free of the "urb" pointer. Store the "dev" pointer at the start of the function to avoid this issue. CVE-2024-50267 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50267.html CVE-2024-50267 https://bugzilla.suse.com/1233456 SUSE Bug 1233456 https://bugzilla.suse.com/1233711 SUSE Bug 1233711 In the Linux kernel, the following vulnerability has been resolved: idpf: avoid vport access in idpf_get_link_ksettings When the device control plane is removed or the platform running device control plane is rebooted, a reset is detected on the driver. On driver reset, it releases the resources and waits for the reset to complete. If the reset fails, it takes the error path and releases the vport lock. At this time if the monitoring tools tries to access link settings, it call traces for accessing released vport pointer. To avoid it, move link_speed_mbps to netdev_priv structure which removes the dependency on vport pointer and the vport lock in idpf_get_link_ksettings. Also use netif_carrier_ok() to check the link status and adjust the offsetof to use link_up instead of link_speed_mbps. CVE-2024-50274 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50274.html CVE-2024-50274 https://bugzilla.suse.com/1233463 SUSE Bug 1233463 https://bugzilla.suse.com/1235104 SUSE Bug 1235104 In the Linux kernel, the following vulnerability has been resolved: dm cache: fix out-of-bounds access to the dirty bitset when resizing dm-cache checks the dirty bits of the cache blocks to be dropped when shrinking the fast device, but an index bug in bitset iteration causes out-of-bounds access. Reproduce steps: 1. create a cache device of 1024 cache blocks (128 bytes dirty bitset) dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --table "0 131072 linear /dev/sdc 8192" dmsetup create corig --table "0 524288 linear /dev/sdc 262144" dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 oflag=direct dmsetup create cache --table "0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0" 2. shrink the fast device to 512 cache blocks, triggering out-of-bounds access to the dirty bitset (offset 0x80) dmsetup suspend cache dmsetup reload cdata --table "0 65536 linear /dev/sdc 8192" dmsetup resume cdata dmsetup resume cache KASAN reports: BUG: KASAN: vmalloc-out-of-bounds in cache_preresume+0x269/0x7b0 Read of size 8 at addr ffffc900000f3080 by task dmsetup/131 (...snip...) The buggy address belongs to the virtual mapping at [ffffc900000f3000, ffffc900000f5000) created by: cache_ctr+0x176a/0x35f0 (...snip...) Memory state around the buggy address: ffffc900000f2f80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ffffc900000f3000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffffc900000f3080: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ^ ffffc900000f3100: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ffffc900000f3180: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 Fix by making the index post-incremented. CVE-2024-50279 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50279.html CVE-2024-50279 https://bugzilla.suse.com/1233468 SUSE Bug 1233468 https://bugzilla.suse.com/1233708 SUSE Bug 1233708 In the Linux kernel, the following vulnerability has been resolved: media: cx24116: prevent overflows on SNR calculus as reported by Coverity, if reading SNR registers fail, a negative number will be returned, causing an underflow when reading SNR registers. Prevent that. CVE-2024-50290 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50290.html CVE-2024-50290 https://bugzilla.suse.com/1225742 SUSE Bug 1225742 https://bugzilla.suse.com/1233479 SUSE Bug 1233479 https://bugzilla.suse.com/1233681 SUSE Bug 1233681 In the Linux kernel, the following vulnerability has been resolved: security/keys: fix slab-out-of-bounds in key_task_permission KASAN reports an out of bounds read: BUG: KASAN: slab-out-of-bounds in __kuid_val include/linux/uidgid.h:36 BUG: KASAN: slab-out-of-bounds in uid_eq include/linux/uidgid.h:63 [inline] BUG: KASAN: slab-out-of-bounds in key_task_permission+0x394/0x410 security/keys/permission.c:54 Read of size 4 at addr ffff88813c3ab618 by task stress-ng/4362 CPU: 2 PID: 4362 Comm: stress-ng Not tainted 5.10.0-14930-gafbffd6c3ede #15 Call Trace: __dump_stack lib/dump_stack.c:82 [inline] dump_stack+0x107/0x167 lib/dump_stack.c:123 print_address_description.constprop.0+0x19/0x170 mm/kasan/report.c:400 __kasan_report.cold+0x6c/0x84 mm/kasan/report.c:560 kasan_report+0x3a/0x50 mm/kasan/report.c:585 __kuid_val include/linux/uidgid.h:36 [inline] uid_eq include/linux/uidgid.h:63 [inline] key_task_permission+0x394/0x410 security/keys/permission.c:54 search_nested_keyrings+0x90e/0xe90 security/keys/keyring.c:793 This issue was also reported by syzbot. It can be reproduced by following these steps(more details [1]): 1. Obtain more than 32 inputs that have similar hashes, which ends with the pattern '0xxxxxxxe6'. 2. Reboot and add the keys obtained in step 1. The reproducer demonstrates how this issue happened: 1. In the search_nested_keyrings function, when it iterates through the slots in a node(below tag ascend_to_node), if the slot pointer is meta and node->back_pointer != NULL(it means a root), it will proceed to descend_to_node. However, there is an exception. If node is the root, and one of the slots points to a shortcut, it will be treated as a keyring. 2. Whether the ptr is keyring decided by keyring_ptr_is_keyring function. However, KEYRING_PTR_SUBTYPE is 0x2UL, the same as ASSOC_ARRAY_PTR_SUBTYPE_MASK. 3. When 32 keys with the similar hashes are added to the tree, the ROOT has keys with hashes that are not similar (e.g. slot 0) and it splits NODE A without using a shortcut. When NODE A is filled with keys that all hashes are xxe6, the keys are similar, NODE A will split with a shortcut. Finally, it forms the tree as shown below, where slot 6 points to a shortcut. NODE A +------>+---+ ROOT | | 0 | xxe6 +---+ | +---+ xxxx | 0 | shortcut : : xxe6 +---+ | +---+ xxe6 : : | | | xxe6 +---+ | +---+ | 6 |---+ : : xxe6 +---+ +---+ xxe6 : : | f | xxe6 +---+ +---+ xxe6 | f | +---+ 4. As mentioned above, If a slot(slot 6) of the root points to a shortcut, it may be mistakenly transferred to a key*, leading to a read out-of-bounds read. To fix this issue, one should jump to descend_to_node if the ptr is a shortcut, regardless of whether the node is root or not. [1] https://lore.kernel.org/linux-kernel/1cfa878e-8c7b-4570-8606-21daf5e13ce7@huaweicloud.com/ [jarkko: tweaked the commit message a bit to have an appropriate closes tag.] CVE-2024-50301 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50301.html CVE-2024-50301 https://bugzilla.suse.com/1233490 SUSE Bug 1233490 https://bugzilla.suse.com/1233680 SUSE Bug 1233680 In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report. CVE-2024-50302 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-50302.html CVE-2024-50302 https://bugzilla.suse.com/1233491 SUSE Bug 1233491 https://bugzilla.suse.com/1233679 SUSE Bug 1233679 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2024-53061 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-53061.html CVE-2024-53061 https://bugzilla.suse.com/1233555 SUSE Bug 1233555 https://bugzilla.suse.com/1233621 SUSE Bug 1233621 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2024-53063 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-53063.html CVE-2024-53063 https://bugzilla.suse.com/1225742 SUSE Bug 1225742 https://bugzilla.suse.com/1233557 SUSE Bug 1233557 https://bugzilla.suse.com/1233619 SUSE Bug 1233619 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. CVE-2024-53068 SUSE Linux Enterprise Micro 5.3:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.3:kernel-source-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-rt-5.14.21-150400.15.103.1 SUSE Linux Enterprise Micro 5.4:kernel-source-rt-5.14.21-150400.15.103.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2024/suse-su-20244345-1/ https://www.suse.com/security/cve/CVE-2024-53068.html CVE-2024-53068 https://bugzilla.suse.com/1233561 SUSE Bug 1233561 https://bugzilla.suse.com/1233618 SUSE Bug 1233618