Security update for the Linux Kernel SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2024:4317-1 Final 1 1 2024-12-13T15:32:18Z current 2024-12-13T15:32:18Z 2024-12-13T15:32:18Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for the Linux Kernel The SUSE Linux Enterprise 15 SP3 RT kernel was updated to receive various security bugfixes. The following security bugs were fixed: - CVE-2023-52524: net: nfc: llcp: Add lock when modifying device list (bsc#1220927). - CVE-2024-49925: fbdev: efifb: Register sysfs groups through driver core (bsc#1232224). - 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-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-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). The following non-security bugs were fixed: - e1000e: Correct NVM checksum verification flow (jsc#SLE-8100). - e1000e: Do not take care about recovery NVM checksum (jsc#SLE-8100). - ena: Remove rcu_read_lock() around XDP program invocation (bsc#1198778). - ethernet: amazon: ena: A typo fix in the file ena_com.h (bsc#1198778). - initramfs: avoid filename buffer overrun (bsc#1232436). - kernel-binary: Enable livepatch package only when livepatch is enabled (bsc#1218644). - net: ena: Add capabilities field with support for ENI stats capability (bsc#1198778). - net: ena: Add debug prints for invalid req_id resets (bsc#1198778). - net: ena: Change ENI stats support check to use capabilities field (bsc#1198778). - net: ena: Change return value of ena_calc_io_queue_size() to void (bsc#1198778). - net: ena: Change the name of bad_csum variable (bsc#1198778). - net: ena: Extract recurring driver reset code into a function (bsc#1198778). - net: ena: Flush XDP packets on error (bsc#1198778). - net: ena: Improve error logging in driver (bsc#1198778). - net: ena: Move reset completion print to the reset function (bsc#1198778). - net: ena: Remove ena_calc_queue_size_ctx struct (bsc#1198778). - net: ena: Remove module param and change message severity (bsc#1198778). - net: ena: Remove redundant return code check (bsc#1198778). - net: ena: Remove unused code (bsc#1198778). - net: ena: Set tx_info->xdpf value to NULL (bsc#1198778). - net: ena: Update XDP verdict upon failure (bsc#1198778). - net: ena: Use bitmask to indicate packet redirection (bsc#1198778). - net: ena: Use dev_alloc() in RX buffer allocation (bsc#1198778). - net: ena: add device distinct log prefix to files (bsc#1198778). - net: ena: add jiffies of last napi call to stats (bsc#1198778). - net: ena: aggregate doorbell common operations into a function (bsc#1198778). - net: ena: aggregate stats increase into a function (bsc#1198778). - net: ena: fix DMA mapping function issues in XDP (bsc#1198778). - net: ena: fix coding style nits (bsc#1198778). - net: ena: fix inaccurate print type (bsc#1198778). - net: ena: introduce XDP redirect implementation (bsc#1198778). - net: ena: introduce ndo_xdp_xmit() function for XDP_REDIRECT (bsc#1198778). - net: ena: make symbol 'ena_alloc_map_page' static (bsc#1198778). - net: ena: re-organize code to improve readability (bsc#1198778). - net: ena: remove extra words from comments (bsc#1198778). - net: ena: store values in their appropriate variables types (bsc#1198778). - net: ena: use build_skb() in RX path (bsc#1198778). - net: ena: use constant value for net_device allocation (bsc#1198778). - net: ena: use xdp_frame in XDP TX flow (bsc#1198778). - net: ena: use xdp_return_frame() to free xdp frames (bsc#1198778). - tools headers: Grab copy of linux/const.h, needed by linux/bits.h (bsc#1154353). The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-2024-4317,SUSE-SUSE-MicroOS-5.1-2024-4317,SUSE-SUSE-MicroOS-5.2-2024-4317 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-20244317-1/ Link for SUSE-SU-2024:4317-1 https://lists.suse.com/pipermail/sle-security-updates/2024-December/020000.html E-Mail link for SUSE-SU-2024:4317-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1154353 SUSE Bug 1154353 https://bugzilla.suse.com/1198778 SUSE Bug 1198778 https://bugzilla.suse.com/1218644 SUSE Bug 1218644 https://bugzilla.suse.com/1220927 SUSE Bug 1220927 https://bugzilla.suse.com/1231939 SUSE Bug 1231939 https://bugzilla.suse.com/1231940 SUSE Bug 1231940 https://bugzilla.suse.com/1231958 SUSE Bug 1231958 https://bugzilla.suse.com/1231962 SUSE Bug 1231962 https://bugzilla.suse.com/1231991 SUSE Bug 1231991 https://bugzilla.suse.com/1231992 SUSE Bug 1231992 https://bugzilla.suse.com/1231995 SUSE Bug 1231995 https://bugzilla.suse.com/1232006 SUSE Bug 1232006 https://bugzilla.suse.com/1232163 SUSE Bug 1232163 https://bugzilla.suse.com/1232172 SUSE Bug 1232172 https://bugzilla.suse.com/1232224 SUSE Bug 1232224 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/1233293 SUSE Bug 1233293 https://bugzilla.suse.com/1233453 SUSE Bug 1233453 https://bugzilla.suse.com/1233456 SUSE Bug 1233456 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://www.suse.com/security/cve/CVE-2022-48985/ SUSE CVE CVE-2022-48985 page https://www.suse.com/security/cve/CVE-2022-49006/ SUSE CVE CVE-2022-49006 page https://www.suse.com/security/cve/CVE-2022-49010/ SUSE CVE CVE-2022-49010 page https://www.suse.com/security/cve/CVE-2022-49011/ SUSE CVE CVE-2022-49011 page https://www.suse.com/security/cve/CVE-2022-49019/ SUSE CVE CVE-2022-49019 page https://www.suse.com/security/cve/CVE-2022-49021/ SUSE CVE CVE-2022-49021 page https://www.suse.com/security/cve/CVE-2022-49022/ SUSE CVE CVE-2022-49022 page https://www.suse.com/security/cve/CVE-2022-49029/ SUSE CVE CVE-2022-49029 page https://www.suse.com/security/cve/CVE-2022-49031/ SUSE CVE CVE-2022-49031 page https://www.suse.com/security/cve/CVE-2022-49032/ SUSE CVE CVE-2022-49032 page https://www.suse.com/security/cve/CVE-2023-52524/ SUSE CVE CVE-2023-52524 page https://www.suse.com/security/cve/CVE-2024-49925/ SUSE CVE CVE-2024-49925 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-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-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 SUSE Linux Enterprise Micro 5.1 SUSE Linux Enterprise Micro 5.2 cluster-md-kmp-rt-5.3.18-150300.194.1 cluster-md-kmp-rt_debug-5.3.18-150300.194.1 dlm-kmp-rt-5.3.18-150300.194.1 dlm-kmp-rt_debug-5.3.18-150300.194.1 gfs2-kmp-rt-5.3.18-150300.194.1 gfs2-kmp-rt_debug-5.3.18-150300.194.1 kernel-devel-rt-5.3.18-150300.194.1 kernel-rt-5.3.18-150300.194.1 kernel-rt-devel-5.3.18-150300.194.1 kernel-rt-extra-5.3.18-150300.194.1 kernel-rt-livepatch-devel-5.3.18-150300.194.1 kernel-rt-optional-5.3.18-150300.194.1 kernel-rt_debug-5.3.18-150300.194.1 kernel-rt_debug-devel-5.3.18-150300.194.1 kernel-rt_debug-extra-5.3.18-150300.194.1 kernel-rt_debug-livepatch-devel-5.3.18-150300.194.1 kernel-rt_debug-optional-5.3.18-150300.194.1 kernel-source-rt-5.3.18-150300.194.1 kernel-syms-rt-5.3.18-150300.194.1 kselftests-kmp-rt-5.3.18-150300.194.1 kselftests-kmp-rt_debug-5.3.18-150300.194.1 ocfs2-kmp-rt-5.3.18-150300.194.1 ocfs2-kmp-rt_debug-5.3.18-150300.194.1 reiserfs-kmp-rt-5.3.18-150300.194.1 reiserfs-kmp-rt_debug-5.3.18-150300.194.1 kernel-rt-5.3.18-150300.194.1 as a component of SUSE Linux Enterprise Micro 5.1 kernel-source-rt-5.3.18-150300.194.1 as a component of SUSE Linux Enterprise Micro 5.1 kernel-rt-5.3.18-150300.194.1 as a component of SUSE Linux Enterprise Micro 5.2 kernel-source-rt-5.3.18-150300.194.1 as a component of SUSE Linux Enterprise Micro 5.2 In the Linux kernel, the following vulnerability has been resolved: net: mana: Fix race on per-CQ variable napi work_done After calling napi_complete_done(), the NAPIF_STATE_SCHED bit may be cleared, and another CPU can start napi thread and access per-CQ variable, cq->work_done. If the other thread (for example, from busy_poll) sets it to a value >= budget, this thread will continue to run when it should stop, and cause memory corruption and panic. To fix this issue, save the per-CQ work_done variable in a local variable before napi_complete_done(), so it won't be corrupted by a possible concurrent thread after napi_complete_done(). Also, add a flag bit to advertise to the NIC firmware: the NAPI work_done variable race is fixed, so the driver is able to reliably support features like busy_poll. CVE-2022-48985 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-1/ https://www.suse.com/security/cve/CVE-2022-48985.html CVE-2022-48985 https://bugzilla.suse.com/1231958 SUSE Bug 1231958 In the Linux kernel, the following vulnerability has been resolved: tracing: Free buffers when a used dynamic event is removed After 65536 dynamic events have been added and removed, the "type" field of the event then uses the first type number that is available (not currently used by other events). A type number is the identifier of the binary blobs in the tracing ring buffer (known as events) to map them to logic that can parse the binary blob. The issue is that if a dynamic event (like a kprobe event) is traced and is in the ring buffer, and then that event is removed (because it is dynamic, which means it can be created and destroyed), if another dynamic event is created that has the same number that new event's logic on parsing the binary blob will be used. To show how this can be an issue, the following can crash the kernel: # cd /sys/kernel/tracing # for i in `seq 65536`; do echo 'p:kprobes/foo do_sys_openat2 $arg1:u32' > kprobe_events # done For every iteration of the above, the writing to the kprobe_events will remove the old event and create a new one (with the same format) and increase the type number to the next available on until the type number reaches over 65535 which is the max number for the 16 bit type. After it reaches that number, the logic to allocate a new number simply looks for the next available number. When an dynamic event is removed, that number is then available to be reused by the next dynamic event created. That is, once the above reaches the max number, the number assigned to the event in that loop will remain the same. Now that means deleting one dynamic event and created another will reuse the previous events type number. This is where bad things can happen. After the above loop finishes, the kprobes/foo event which reads the do_sys_openat2 function call's first parameter as an integer. # echo 1 > kprobes/foo/enable # cat /etc/passwd > /dev/null # cat trace cat-2211 [005] .... 2007.849603: foo: (do_sys_openat2+0x0/0x130) arg1=4294967196 cat-2211 [005] .... 2007.849620: foo: (do_sys_openat2+0x0/0x130) arg1=4294967196 cat-2211 [005] .... 2007.849838: foo: (do_sys_openat2+0x0/0x130) arg1=4294967196 cat-2211 [005] .... 2007.849880: foo: (do_sys_openat2+0x0/0x130) arg1=4294967196 # echo 0 > kprobes/foo/enable Now if we delete the kprobe and create a new one that reads a string: # echo 'p:kprobes/foo do_sys_openat2 +0($arg2):string' > kprobe_events And now we can the trace: # cat trace sendmail-1942 [002] ..... 530.136320: foo: (do_sys_openat2+0x0/0x240) arg1= cat-2046 [004] ..... 530.930817: foo: (do_sys_openat2+0x0/0x240) arg1="������������������������������������������������������������������������������������������������" cat-2046 [004] ..... 530.930961: foo: (do_sys_openat2+0x0/0x240) arg1="������������������������������������������������������������������������������������������������" cat-2046 [004] ..... 530.934278: foo: (do_sys_openat2+0x0/0x240) arg1="������������������������������������������������������������������������������������������������" cat-2046 [004] ..... 530.934563: foo: (do_sys_openat2+0x0/0x240) arg1="��������������������������������������� ---truncated--- CVE-2022-49006 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-1/ https://www.suse.com/security/cve/CVE-2022-49006.html CVE-2022-49006 https://bugzilla.suse.com/1232163 SUSE Bug 1232163 In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) Check for null before removing sysfs attrs If coretemp_add_core() gets an error then pdata->core_data[indx] is already NULL and has been kfreed. Don't pass that to sysfs_remove_group() as that will crash in sysfs_remove_group(). [Shortened for readability] [91854.020159] sysfs: cannot create duplicate filename '/devices/platform/coretemp.0/hwmon/hwmon2/temp20_label' <cpu offline> [91855.126115] BUG: kernel NULL pointer dereference, address: 0000000000000188 [91855.165103] #PF: supervisor read access in kernel mode [91855.194506] #PF: error_code(0x0000) - not-present page [91855.224445] PGD 0 P4D 0 [91855.238508] Oops: 0000 [#1] PREEMPT SMP PTI ... [91855.342716] RIP: 0010:sysfs_remove_group+0xc/0x80 ... [91855.796571] Call Trace: [91855.810524] coretemp_cpu_offline+0x12b/0x1dd [coretemp] [91855.841738] ? coretemp_cpu_online+0x180/0x180 [coretemp] [91855.871107] cpuhp_invoke_callback+0x105/0x4b0 [91855.893432] cpuhp_thread_fun+0x8e/0x150 ... Fix this by checking for NULL first. CVE-2022-49010 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-1/ https://www.suse.com/security/cve/CVE-2022-49010.html CVE-2022-49010 https://bugzilla.suse.com/1232172 SUSE Bug 1232172 In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() As comment of pci_get_domain_bus_and_slot() says, it returns a pci device with refcount increment, when finish using it, the caller must decrement the reference count by calling pci_dev_put(). So call it after using to avoid refcount leak. CVE-2022-49011 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-1/ https://www.suse.com/security/cve/CVE-2022-49011.html CVE-2022-49011 https://bugzilla.suse.com/1232006 SUSE Bug 1232006 In the Linux kernel, the following vulnerability has been resolved: net: ethernet: nixge: fix NULL dereference In function nixge_hw_dma_bd_release() dereference of NULL pointer priv->rx_bd_v is possible for the case of its allocation failure in nixge_hw_dma_bd_init(). Move for() loop with priv->rx_bd_v dereference under the check for its validity. Found by Linux Verification Center (linuxtesting.org) with SVACE. CVE-2022-49019 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-1/ https://www.suse.com/security/cve/CVE-2022-49019.html CVE-2022-49019 https://bugzilla.suse.com/1231940 SUSE Bug 1231940 In the Linux kernel, the following vulnerability has been resolved: net: phy: fix null-ptr-deref while probe() failed I got a null-ptr-deref report as following when doing fault injection test: BUG: kernel NULL pointer dereference, address: 0000000000000058 Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 1 PID: 253 Comm: 507-spi-dm9051 Tainted: G B N 6.1.0-rc3+ Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:klist_put+0x2d/0xd0 Call Trace: <TASK> klist_remove+0xf1/0x1c0 device_release_driver_internal+0x23e/0x2d0 bus_remove_device+0x1bd/0x240 device_del+0x357/0x770 phy_device_remove+0x11/0x30 mdiobus_unregister+0xa5/0x140 release_nodes+0x6a/0xa0 devres_release_all+0xf8/0x150 device_unbind_cleanup+0x19/0xd0 //probe path: phy_device_register() device_add() phy_connect phy_attach_direct() //set device driver probe() //it's failed, driver is not bound device_bind_driver() // probe failed, it's not called //remove path: phy_device_remove() device_del() device_release_driver_internal() __device_release_driver() //dev->drv is not NULL klist_remove() <- knode_driver is not added yet, cause null-ptr-deref In phy_attach_direct(), after setting the 'dev->driver', probe() fails, device_bind_driver() is not called, so the knode_driver->n_klist is not set, then it causes null-ptr-deref in __device_release_driver() while deleting device. Fix this by setting dev->driver to NULL in the error path in phy_attach_direct(). CVE-2022-49021 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-1/ https://www.suse.com/security/cve/CVE-2022-49021.html CVE-2022-49021 https://bugzilla.suse.com/1231939 SUSE Bug 1231939 In the Linux kernel, the following vulnerability has been resolved: wifi: mac8021: fix possible oob access in ieee80211_get_rate_duration Fix possible out-of-bound access in ieee80211_get_rate_duration routine as reported by the following UBSAN report: UBSAN: array-index-out-of-bounds in net/mac80211/airtime.c:455:47 index 15 is out of range for type 'u16 [12]' CPU: 2 PID: 217 Comm: kworker/u32:10 Not tainted 6.1.0-060100rc3-generic Hardware name: Acer Aspire TC-281/Aspire TC-281, BIOS R01-A2 07/18/2017 Workqueue: mt76 mt76u_tx_status_data [mt76_usb] Call Trace: <TASK> show_stack+0x4e/0x61 dump_stack_lvl+0x4a/0x6f dump_stack+0x10/0x18 ubsan_epilogue+0x9/0x43 __ubsan_handle_out_of_bounds.cold+0x42/0x47 ieee80211_get_rate_duration.constprop.0+0x22f/0x2a0 [mac80211] ? ieee80211_tx_status_ext+0x32e/0x640 [mac80211] ieee80211_calc_rx_airtime+0xda/0x120 [mac80211] ieee80211_calc_tx_airtime+0xb4/0x100 [mac80211] mt76x02_send_tx_status+0x266/0x480 [mt76x02_lib] mt76x02_tx_status_data+0x52/0x80 [mt76x02_lib] mt76u_tx_status_data+0x67/0xd0 [mt76_usb] process_one_work+0x225/0x400 worker_thread+0x50/0x3e0 ? process_one_work+0x400/0x400 kthread+0xe9/0x110 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 CVE-2022-49022 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-1/ https://www.suse.com/security/cve/CVE-2022-49022.html CVE-2022-49022 https://bugzilla.suse.com/1231962 SUSE Bug 1231962 In the Linux kernel, the following vulnerability has been resolved: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails Smatch report warning as follows: drivers/hwmon/ibmpex.c:509 ibmpex_register_bmc() warn: '&data->list' not removed from list If ibmpex_find_sensors() fails in ibmpex_register_bmc(), data will be freed, but data->list will not be removed from driver_data.bmc_data, then list traversal may cause UAF. Fix by removeing it from driver_data.bmc_data before free(). CVE-2022-49029 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-1/ https://www.suse.com/security/cve/CVE-2022-49029.html CVE-2022-49029 https://bugzilla.suse.com/1231995 SUSE Bug 1231995 In the Linux kernel, the following vulnerability has been resolved: iio: health: afe4403: Fix oob read in afe4403_read_raw KASAN report out-of-bounds read as follows: BUG: KASAN: global-out-of-bounds in afe4403_read_raw+0x42e/0x4c0 Read of size 4 at addr ffffffffc02ac638 by task cat/279 Call Trace: afe4403_read_raw iio_read_channel_info dev_attr_show The buggy address belongs to the variable: afe4403_channel_leds+0x18/0xffffffffffffe9e0 This issue can be reproduced by singe command: $ cat /sys/bus/spi/devices/spi0.0/iio\:device0/in_intensity6_raw The array size of afe4403_channel_leds is less than channels, so access with chan->address cause OOB read in afe4403_read_raw. Fix it by moving access before use it. CVE-2022-49031 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-1/ https://www.suse.com/security/cve/CVE-2022-49031.html CVE-2022-49031 https://bugzilla.suse.com/1231992 SUSE Bug 1231992 In the Linux kernel, the following vulnerability has been resolved: iio: health: afe4404: Fix oob read in afe4404_[read|write]_raw KASAN report out-of-bounds read as follows: BUG: KASAN: global-out-of-bounds in afe4404_read_raw+0x2ce/0x380 Read of size 4 at addr ffffffffc00e4658 by task cat/278 Call Trace: afe4404_read_raw iio_read_channel_info dev_attr_show The buggy address belongs to the variable: afe4404_channel_leds+0x18/0xffffffffffffe9c0 This issue can be reproduce by singe command: $ cat /sys/bus/i2c/devices/0-0058/iio\:device0/in_intensity6_raw The array size of afe4404_channel_leds and afe4404_channel_offdacs are less than channels, so access with chan->address cause OOB read in afe4404_[read|write]_raw. Fix it by moving access before use them. CVE-2022-49032 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-1/ https://www.suse.com/security/cve/CVE-2022-49032.html CVE-2022-49032 https://bugzilla.suse.com/1231991 SUSE Bug 1231991 In the Linux kernel, the following vulnerability has been resolved: net: nfc: llcp: Add lock when modifying device list The device list needs its associated lock held when modifying it, or the list could become corrupted, as syzbot discovered. CVE-2023-52524 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-1/ https://www.suse.com/security/cve/CVE-2023-52524.html CVE-2023-52524 https://bugzilla.suse.com/1220927 SUSE Bug 1220927 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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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 ** REJECT ** This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. CVE-2024-50089 SUSE Linux Enterprise Micro 5.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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: 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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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: 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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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.1:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.1:kernel-source-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-rt-5.3.18-150300.194.1 SUSE Linux Enterprise Micro 5.2:kernel-source-rt-5.3.18-150300.194.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-20244317-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