CVE-2023-52629

In the Linux kernel, the following vulnerability has been resolved: sh: push-switch: Reorder cleanup operations to avoid use-after-free bug The original code puts flush_work() before timer_shutdown_sync() in switch_drv_remove(). Although we use flush_work() to stop the worker, it could be rescheduled in switch_timer(). As a result, a use-after-free bug can occur. The details are shown below: (cpu 0) | (cpu 1) switch_drv_remove() | flush_work() | ... | switch_timer // timer | schedule_work(&psw->work) timer_shutdown_sync() | ... | switch_work_handler // worker kfree(psw) // free | | psw->state = 0 // use This patch puts timer_shutdown_sync() before flush_work() to mitigate the bugs. As a result, the worker and timer will be stopped safely before the deallocate operations.

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

x86/kvm: Disable kvmclock on all CPUs on shutdown

Currenly, we disable kvmclock from machine_shutdown() hook and this only happens for boot CPU. We need to disable it for all CPUs to guard against memory corruption e.g. on restore from hibernate.

Note, writing '0' to kvmclock MSR doesn't clear memory location, it just prevents hypervisor from updating the location so for the short while after write and while CPU is still alive, the clock remains usable and correct so we don't need to switch to some other clocksource.(CVE-2021-47110)

In the Linux kernel, the following vulnerability has been resolved:

i40e: Fix NULL ptr dereference on VSI filter sync

Remove the reason of null pointer dereference in sync VSI filters. Added new I40E_VSI_RELEASING flag to signalize deleting and releasing of VSI resources to sync this thread with sync filters subtask. Without this patch it is possible to start update the VSI filter list after VSI is removed, that's causing a kernel oops.(CVE-2021-47184)

In the Linux kernel, the following vulnerability has been resolved:

erofs: fix pcluster use-after-free on UP platforms

During stress testing with CONFIG_SMP disabled, KASAN reports as below:

================================================================== BUG: KASAN: use-after-free in __mutex_lock+0xe5/0xc30 Read of size 8 at addr ffff8881094223f8 by task stress/7789

CPU: 0 PID: 7789 Comm: stress Not tainted 6.0.0-rc1-00002-g0d53d2e882f9 #3 Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 Call Trace: <TASK> .. __mutex_lock+0xe5/0xc30 .. z_erofs_do_read_page+0x8ce/0x1560 .. z_erofs_readahead+0x31c/0x580 .. Freed by task 7787 kasan_save_stack+0x1e/0x40 kasan_set_track+0x20/0x30 kasan_set_free_info+0x20/0x40 __kasan_slab_free+0x10c/0x190 kmem_cache_free+0xed/0x380 rcu_core+0x3d5/0xc90 __do_softirq+0x12d/0x389

Last potentially related work creation: kasan_save_stack+0x1e/0x40 __kasan_record_aux_stack+0x97/0xb0 call_rcu+0x3d/0x3f0 erofs_shrink_workstation+0x11f/0x210 erofs_shrink_scan+0xdc/0x170 shrink_slab.constprop.0+0x296/0x530 drop_slab+0x1c/0x70 drop_caches_sysctl_handler+0x70/0x80 proc_sys_call_handler+0x20a/0x2f0 vfs_write+0x555/0x6c0 ksys_write+0xbe/0x160 do_syscall_64+0x3b/0x90

The root cause is that erofs_workgroup_unfreeze() doesn't reset to orig_val thus it causes a race that the pcluster reuses unexpectedly before freeing.

Since UP platforms are quite rare now, such path becomes unnecessary. Let's drop such specific-designed path directly instead.(CVE-2022-48674)

In the Linux kernel, the following vulnerability has been resolved:

hwrng: core - Fix page fault dead lock on mmap-ed hwrng

There is a dead-lock in the hwrng device read path. This triggers when the user reads from /dev/hwrng into memory also mmap-ed from /dev/hwrng. The resulting page fault triggers a recursive read which then dead-locks.

Fix this by using a stack buffer when calling copy_to_user.(CVE-2023-52615)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nf_tables: disallow timeout for anonymous sets

Never used from userspace, disallow these parameters.(CVE-2023-52620)

In the Linux kernel, the following vulnerability has been resolved:

SUNRPC: Fix a suspicious RCU usage warning

I received the following warning while running cthon against an ontap server running pNFS:

[ 57.202521] ============================= [ 57.202522] WARNING: suspicious RCU usage [ 57.202523] 6.7.0-rc3-g2cc14f52aeb7 #41492 Not tainted [ 57.202525] ----------------------------- [ 57.202525] net/sunrpc/xprtmultipath.c:349 RCU-list traversed in non-reader section!! [ 57.202527] other info that might help us debug this:

[ 57.202528] …

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

tun: avoid double free in tun_free_netdev

Avoid double free in tun_free_netdev() by moving the dev->tstats and tun->security allocs to a new ndo_init routine (tun_net_init()) that will be called by register_netdevice(). ndo_init is paired with the desctructor (tun_free_netdev()), so if there's an error in register_netdevice() the destructor will handle the frees.

BUG: KASAN: double-free or invalid-free in selinux_tun_dev_free_security+0x1a/0x20 security/selinux/hooks.c:5605

CPU: 0 PID: 25750 Comm: syz-executor416 Not tainted 5.16.0-rc2-syzk #1 Hardware name: Red Hat KVM, BIOS Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x89/0xb5 lib/dump_stack.c:106 print_address_description.constprop.9+0x28/0x160 mm/kasan/report.c:247 kasan_report_invalid_free+0x55/0x80 mm/kasan/report.c:372 ____kasan_slab_free mm/kasan/common.c:346 [inline] __kasan_slab_free+0x107/0x120 mm/kasan/common.c:374 kasan_slab_free include/linux/kasan.h:235 [inline] slab_free_hook mm/slub.c:1723 [inline] slab_free_freelist_hook mm/slub.c:1749 [inline] slab_free mm/slub.c:3513 [inline] kfree+0xac/0x2d0 mm/slub.c:4561 selinux_tun_dev_free_security+0x1a/0x20 security/selinux/hooks.c:5605 security_tun_dev_free_security+0x4f/0x90 security/security.c:2342 tun_free_netdev+0xe6/0x150 drivers/net/tun.c:2215 netdev_run_todo+0x4df/0x840 net/core/dev.c:10627 rtnl_unlock+0x13/0x20 net/core/rtnetlink.c:112 __tun_chr_ioctl+0x80c/0x2870 drivers/net/tun.c:3302 tun_chr_ioctl+0x2f/0x40 drivers/net/tun.c:3311 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl fs/ioctl.c:860 [inline] __x64_sys_ioctl+0x19d/0x220 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3a/0x80 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae(CVE-2021-47082)

In the Linux kernel, the following vulnerability has been resolved:

x86/kvm: Disable kvmclock on all CPUs on shutdown

Currenly, we disable kvmclock from machine_shutdown() hook and this only happens for boot CPU. We need to disable it for all CPUs to guard against memory corruption e.g. on restore from hibernate.

Note, writing '0' to kvmclock MSR doesn't clear memory location, it just prevents hypervisor from updating the location so for the short while after write and while CPU is still alive, the clock remains usable and correct so we don't need to switch to some other clocksource.(CVE-2021-47110)

In the Linux kernel, the following vulnerability has been resolved:

i40e: Fix NULL ptr dereference on VSI filter sync

Remove the reason of null pointer dereference in sync VSI filters. Added new I40E_VSI_RELEASING flag to signalize deleting and releasing of VSI resources to sync this thread with sync filters subtask. Without this patch it is possible to start update the VSI filter list after VSI is removed, that's causing a kernel oops.(CVE-2021-47184)

In the Linux kernel, the following vulnerability has been resolved:

erofs: fix pcluster use-after-free on UP platforms

During stress testing with CONFIG_SMP disabled, KASAN reports as below:

================================================================== BUG: KASAN: use-after-free in __mutex_lock+0xe5/0xc30 Read of size 8 at addr ffff8881094223f8 by task stress/7789

CPU: 0 PID: 7789 Comm: stress Not tainted 6.0.0-rc1-00002-g0d53d2e882f9 #3 Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 Call Trace: <TASK> .. __mutex_lock+0xe5/0xc30 .. z_erofs_do_read_page+0x8ce/0x1560 .. z_erofs_readahead+0x31c/0x580 .. Freed by task 7787 kasan_save_stack+0x1e/0x40 kasan_set_track+0x20/0x30 kasan_set_free_info+0x20/0x40 __kasan_slab_free+0x10c/0x190 kmem_cache_free+0xed/0x380 rcu_core+0x3d5/0xc90 __do_softirq+0x12d/0x389

Last potentially related work creation: …

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()

memcpy() is called in a loop while 'operation->length' upper bound is not checked and 'data_idx' also increments.(CVE-2022-48632)

In the Linux kernel, the following vulnerability has been resolved:

mm/slub: fix to return errno if kmalloc() fails

In create_unique_id(), kmalloc(, GFP_KERNEL) can fail due to out-of-memory, if it fails, return errno correctly rather than triggering panic via BUG_ON();

kernel BUG at mm/slub.c:5893! Internal error: Oops - BUG: 0 [#1] PREEMPT SMP

Call trace: sysfs_slab_add+0x258/0x260 mm/slub.c:5973 __kmem_cache_create+0x60/0x118 mm/slub.c:4899 create_cache mm/slab_common.c:229 [inline] kmem_cache_create_usercopy+0x19c/0x31c mm/slab_common.c:335 kmem_cache_create+0x1c/0x28 mm/slab_common.c:390 f2fs_kmem_cache_create fs/f2fs/f2fs.h:2766 [inline] f2fs_init_xattr_caches+0x78/0xb4 fs/f2fs/xattr.c:808 f2fs_fill_super+0x1050/0x1e0c fs/f2fs/super.c:4149 mount_bdev+0x1b8/0x210 fs/super.c:1400 f2fs_mount+0x44/0x58 fs/f2fs/super.c:4512 legacy_get_tree+0x30/0x74 fs/fs_context.c:610 vfs_get_tree+0x40/0x140 fs/super.c:1530 do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040 path_mount+0x358/0x914 fs/namespace.c:3370 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount fs/namespace.c:3568 [inline] __arm64_sys_mount+0x2f8/0x408 fs/namespace.c:3568(CVE-2022-48659)

In the Linux kernel, the following vulnerability has been resolved:

gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully

When running gpio test on nxp-ls1028 platform with below command gpiomon --num-events=3 --rising-edge gpiochip1 25 There will be a warning trace as below: Call trace: free_irq+0x204/0x360 lineevent_free+0x64/0x70 gpio_ioctl+0x598/0x6a0 __arm64_sys_ioctl+0xb4/0x100 invoke_syscall+0x5c/0x130 ...... el0t_64_sync+0x1a0/0x1a4 The reason of this issue is that calling request_threaded_irq() function failed, and then lineevent_free() is invoked to release the resource. Since the lineevent_state::irq was already set, so the subsequent invocation of free_irq() would trigger the above warning call trace. To fix this issue, set the lineevent_state::irq after the IRQ register successfully.(CVE-2022-48660)

In the Linux kernel, the following vulnerability has been resolved:

binder: fix race between mmput() and do_exit()

Task A calls binder_update_page_range() to allocate and insert pages on a remote address space from Task B. For this, Task A pins the remote mm via mmget_not_zero() first. This can race with Task B do_exit() and the final mmput() refcount decrement will come from Task A.

Task A | Task B ------------------+------------------ mmget_not_zero() | | do_exit() | exit_mm() | mmput() mmput() | exit_mmap() | remove_vma() | fput() |

In this case, the work of ____fput() from Task B is queued up in Task A as TWA_RESUME. So in theory, Task A returns to userspace and the cleanup work gets executed. However, Task A instead sleep, waiting for a reply from Task B that never comes (it's dead).

This means the binder_deferred_release() is blocked until an unrelated binder event forces Task A to go back to userspace. All the associated death notifications will also be delayed until then.

In order to fix this use mmput_async() that will schedule the work in the corresponding mm->async_put_work WQ instead of Task A.(CVE-2023-52609)

In the Linux kernel, the following vulnerability has been resolved:

hwrng: core - Fix page fault dead lock on mmap-ed hwrng

There is a dead-lock in the hwrng device read path. This triggers when the user reads from /dev/hwrng…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

mm/slub: fix to return errno if kmalloc() fails

In create_unique_id(), kmalloc(, GFP_KERNEL) can fail due to out-of-memory, if it fails, return errno correctly rather than triggering panic via BUG_ON();

kernel BUG at mm/slub.c:5893! Internal error: Oops - BUG: 0 [#1] PREEMPT SMP

Call trace: sysfs_slab_add+0x258/0x260 mm/slub.c:5973 __kmem_cache_create+0x60/0x118 mm/slub.c:4899 create_cache mm/slab_common.c:229 [inline] kmem_cache_create_usercopy+0x19c/0x31c mm/slab_common.c:335 kmem_cache_create+0x1c/0x28 mm/slab_common.c:390 f2fs_kmem_cache_create fs/f2fs/f2fs.h:2766 [inline] f2fs_init_xattr_caches+0x78/0xb4 fs/f2fs/xattr.c:808 f2fs_fill_super+0x1050/0x1e0c fs/f2fs/super.c:4149 mount_bdev+0x1b8/0x210 fs/super.c:1400 f2fs_mount+0x44/0x58 fs/f2fs/super.c:4512 legacy_get_tree+0x30/0x74 fs/fs_context.c:610 vfs_get_tree+0x40/0x140 fs/super.c:1530 do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040 path_mount+0x358/0x914 fs/namespace.c:3370 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount fs/namespace.c:3568 [inline] __arm64_sys_mount+0x2f8/0x408 fs/namespace.c:3568(CVE-2022-48659)

In the Linux kernel, the following vulnerability has been resolved:

gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully

When running gpio test on nxp-ls1028 platform with below command gpiomon --num-events=3 --rising-edge gpiochip1 25 There will be a warning trace as below: Call trace: free_irq+0x204/0x360 lineevent_free+0x64/0x70 gpio_ioctl+0x598/0x6a0 __arm64_sys_ioctl+0xb4/0x100 invoke_syscall+0x5c/0x130 ...... el0t_64_sync+0x1a0/0x1a4 The reason of this issue is that calling request_threaded_irq() function failed, and then lineevent_free() is invoked to release the resource. Since the lineevent_state::irq was already set, so the subsequent invocation of free_irq() would trigger the above warning call trace. To fix this issue, set the lineevent_state::irq after the IRQ register successfully.(CVE-2022-48660)

In the Linux kernel, the following vulnerability has been resolved:

binder: fix race between mmput() and do_exit()

Task A calls binder_update_page_range() to allocate and insert pages on a remote address space from Task B. For this, Task A pins the remote mm via mmget_not_zero() first. This can race with Task B do_exit() and the final mmput() refcount decrement will come from Task A.

Task A | Task B ------------------+------------------ mmget_not_zero() | | do_exit() | exit_mm() | mmput() mmput() | exit_mmap() | remove_vma() | fput() |

In this case, the work of ____fput() from Task B is queued up in Task A as TWA_RESUME. So in theory, Task A returns to userspace and the cleanup work gets executed. However, Task A instead sleep, waiting for a reply from Task B that never comes (it's dead).

This means the binder_deferred_release() is blocked until an unrelated binder event forces Task A to go back to userspace. All the associated death notifications will also be delayed until then.

In order to fix this use mmput_async() that will schedule the work in the corresponding mm->async_put_work WQ instead of Task A.(CVE-2023-52609)

In the Linux kernel, the following vulnerability has been resolved:

hwrng: core - Fix page fault dead lock on mmap-ed hwrng

There is a dead-lock in the hwrng device read path. This triggers when the user reads from /dev/hwrng into memory also mmap-ed from /dev/hwrng. The resulting page fault triggers a recursive read which then dead-locks.

Fix this by using a stack buffer when calling copy_to_user.(CVE-2023-52615)

In the Linux kernel, the following vulnerability has been resolved:

crypto: lib/mpi - Fix unexpected…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

binder: fix race between mmput() and do_exit()

Task A calls binder_update_page_range() to allocate and insert pages on a remote address space from Task B. For this, Task A pins the remote mm via mmget_not_zero() first. This can race with Task B do_exit() and the final mmput() refcount decrement will come from Task A.

Task A | Task B ------------------+------------------ mmget_not_zero() | | do_exit() | exit_mm() | mmput() mmput() | exit_mmap() | remove_vma() | fput() |

In this case, the work of ____fput() from Task B is queued up in Task A as TWA_RESUME. So in theory, Task A returns to userspace and the cleanup work gets executed. However, Task A instead sleep, waiting for a reply from Task B that never comes (it's dead).

This means the binder_deferred_release() is blocked until an unrelated binder event forces Task A to go back to userspace. All the associated death notifications will also be delayed until then.

In order to fix this use mmput_async() that will schedule the work in the corresponding mm->async_put_work WQ instead of Task A.(CVE-2023-52609)

In the Linux kernel, the following vulnerability has been resolved:

hwrng: core - Fix page fault dead lock on mmap-ed hwrng

There is a dead-lock in the hwrng device read path. This triggers when the user reads from /dev/hwrng into memory also mmap-ed from /dev/hwrng. The resulting page fault triggers a recursive read which then dead-locks.

Fix this by using a stack buffer when calling copy_to_user.(CVE-2023-52615)

In the Linux kernel, the following vulnerability has been resolved:

crypto: lib/mpi - Fix unexpected pointer access in mpi_ec_init

When the mpi_ec_ctx structure is initialized, some fields are not cleared, causing a crash when referencing the field when the structure was released. Initially, this issue was ignored because memory for mpi_ec_ctx is allocated with the __GFP_ZERO flag. For example, this error will be triggered when calculating the Za value for SM2 separately.(CVE-2023-52616)

In the Linux kernel, the following vulnerability has been resolved:

bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers

These three bpf_map_{lookup,update,delete}_elem() helpers are also available for sleepable bpf program, so add the corresponding lock assertion for sleepable bpf program, otherwise the following warning will be reported when a sleepable bpf program manipulates bpf map under interpreter mode (aka bpf_jit_enable=0):

WARNING: CPU: 3 PID: 4985 at kernel/bpf/helpers.c:40 ...... CPU: 3 PID: 4985 Comm: test_progs Not tainted 6.6.0+ #2 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) ...... RIP: 0010:bpf_map_lookup_elem+0x54/0x60 ...... Call Trace: <TASK> ? __warn+0xa5/0x240 ? bpf_map_lookup_elem+0x54/0x60 ? report_bug+0x1ba/0x1f0 ? handle_bug+0x40/0x80 ? exc_invalid_op+0x18/0x50 ? asm_exc_invalid_op+0x1b/0x20 ? __pfx_bpf_map_lookup_elem+0x10/0x10 ? rcu_lockdep_current_cpu_online+0x65/0xb0 ? rcu_is_watching+0x23/0x50 ? bpf_map_lookup_elem+0x54/0x60 ? __pfx_bpf_map_lookup_elem+0x10/0x10 ___bpf_prog_run+0x513/0x3b70 __bpf_prog_run32+0x9d/0xd0 ? __bpf_prog_enter_sleepable_recur+0xad/0x120 ? __bpf_prog_enter_sleepable_recur+0x3e/0x120 bpf_trampoline_6442580665+0x4d/0x1000 __x64_sys_getpgid+0x5/0x30 ? do_syscall_64+0x36/0xb0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 </TASK>(CVE-2023-52621)

In the Linux kernel, the following vulnerability has been resolved:

SUNRPC: Fix a suspicious RCU usage warning

I received the following warning while running cthon against an ontap server running pNFS:

[ 57.202521] ============================= […

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

hwrng: core - Fix page fault dead lock on mmap-ed hwrng

There is a dead-lock in the hwrng device read path. This triggers when the user reads from /dev/hwrng into memory also mmap-ed from /dev/hwrng. The resulting page fault triggers a recursive read which then dead-locks.

Fix this by using a stack buffer when calling copy_to_user.(CVE-2023-52615)

In the Linux kernel, the following vulnerability has been resolved:

bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers

These three bpf_map_{lookup,update,delete}_elem() helpers are also available for sleepable bpf program, so add the corresponding lock assertion for sleepable bpf program, otherwise the following warning will be reported when a sleepable bpf program manipulates bpf map under interpreter mode (aka bpf_jit_enable=0):

WARNING: CPU: 3 PID: 4985 at kernel/bpf/helpers.c:40 ...... CPU: 3 PID: 4985 Comm: test_progs Not tainted 6.6.0+ #2 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) ...... RIP: 0010:bpf_map_lookup_elem+0x54/0x60 ...... Call Trace: <TASK> ? __warn+0xa5/0x240 ? bpf_map_lookup_elem+0x54/0x60 ? report_bug+0x1ba/0x1f0 ? handle_bug+0x40/0x80 ? exc_invalid_op+0x18/0x50 ? asm_exc_invalid_op+0x1b/0x20 ? __pfx_bpf_map_lookup_elem+0x10/0x10 ? rcu_lockdep_current_cpu_online+0x65/0xb0 ? rcu_is_watching+0x23/0x50 ? bpf_map_lookup_elem+0x54/0x60 ? __pfx_bpf_map_lookup_elem+0x10/0x10 ___bpf_prog_run+0x513/0x3b70 __bpf_prog_run32+0x9d/0xd0 ? __bpf_prog_enter_sleepable_recur+0xad/0x120 ? __bpf_prog_enter_sleepable_recur+0x3e/0x120 bpf_trampoline_6442580665+0x4d/0x1000 __x64_sys_getpgid+0x5/0x30 ? do_syscall_64+0x36/0xb0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 </TASK>(CVE-2023-52621)

In the Linux kernel, the following vulnerability has been resolved:

SUNRPC: Fix a suspicious RCU usage warning

I received the following warning while running cthon against an ontap server running pNFS:

[ 57.202521] ============================= [ 57.202522] WARNING: suspicious RCU usage [ 57.202523] 6.7.0-rc3-g2cc14f52aeb7 #41492 Not tainted [ 57.202525] ----------------------------- [ 57.202525] net/sunrpc/xprtmultipath.c:349 RCU-list traversed in non-reader section!! [ 57.202527] other info that might help us debug this:

[ 57.202528] rcu_scheduler_active = 2, debug_locks = 1 [ 57.202529] no locks held by test5/3567. [ 57.202530] stack backtrace: [ 57.202532] CPU: 0 PID: 3567 Comm: test5 Not tainted 6.7.0-rc3-g2cc14f52aeb7 #41492 5b09971b4965c0aceba19f3eea324a4a806e227e [ 57.202534] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 2/2/2022 [ 57.202536] Call Trace: [ 57.202537] <TASK> [ 57.202540] dump_stack_lvl+0x77/0xb0 [ 57.202551] lockdep_rcu_suspicious+0x154/0x1a0 [ 57.202556] rpc_xprt_switch_has_addr+0x17c/0x190 [sunrpc ebe02571b9a8ceebf7d98e71675af20c19bdb1f6] [ 57.202596] rpc_clnt_setup_test_and_add_xprt+0x50/0x180 [sunrpc ebe02571b9a8ceebf7d98e71675af20c19bdb1f6] [ 57.202621] ? rpc_clnt_add_xprt+0x254/0x300 [sunrpc ebe02571b9a8ceebf7d98e71675af20c19bdb1f6] [ 57.202646] rpc_clnt_add_xprt+0x27a/0x300 [sunrpc ebe02571b9a8ceebf7d98e71675af20c19bdb1f6] [ 57.202671] ? __pfx_rpc_clnt_setup_test_and_add_xprt+0x10/0x10 [sunrpc ebe02571b9a8ceebf7d98e71675af20c19bdb1f6] [ 57.202696] nfs4_pnfs_ds_connect+0x345/0x760 [nfsv4 c716d88496ded0ea6d289bbea684fa996f9b57a9] [ 57.202728] ? __pfx_nfs4_test_session_trunk+0x10/0x10 [nfsv4 c716d88496ded0ea6d289bbea684fa996f9b57a9] [ 57.202754] nfs4_fl_prepare_ds+0x75/0xc0 [nfs_layout_nfsv41_files e3a4187f18ae8a27b630f9feae6831b584a9360a] [ 57.202760] filelayout_write_pagelist+0x4a/0x200 [nfs_layout_nfsv41_files…

Root has patched CVE-2023-52629 in the linux package for Root:Debian:11. Multiple fixed versions available.

Root has patched CVE-2023-52629 in the linux package for Root:Debian:12. Multiple fixed versions available.

In the Linux kernel, the following vulnerability has been resolved: sh: push-switch: Reorder cleanup operations to avoid use-after-free bug The original code puts flush_work() before timer_shutdown_sync() in switch_drv_remove(). Although we use flush_work() to stop the worker, it could be rescheduled in switch_timer(). As a result, a use-after-free bug can occur. The details are shown below: (cpu 0) | (cpu 1) switch_drv_remove() | flush_work() | ... | switch_timer // timer | schedule_work(&psw->work) timer_shutdown_sync() | ... | switch_work_handler // worker kfree(psw) // free | | psw->state = 0 // use This patch puts timer_shutdown_sync() before flush_work() to mitigate the bugs. As a result, the worker and timer will be stopped safely before the deallocate operations.

• CVE-url: https://ubuntu.com/security/CVE-2024-39487
  • bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set()
• CVE-url: https://ubuntu.com/security/CVE-2023-52760
  • gfs2: Fix slab-use-after-free in gfs2_qd_dealloc
• CVE-url: https://ubuntu.com/security/CVE-2023-52629
  • sh: push-switch: Reorder cleanup operations to avoid use-after-free bug
• CVE-url: https://ubuntu.com/security/CVE-2024-39484
  • mmc: davinci: Don't strip remove function when driver is builtin
• Miscellaneous upstream changes
  • fixup! blk-mq: fix IO hang from sbitmap wakeup race
  • fixup! scsi: qla2xxx: Fix double free of fcport

• CVE-url: https://ubuntu.com/security/CVE-2024-39487
  • bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set()
• CVE-url: https://ubuntu.com/security/CVE-2023-52760
  • gfs2: Fix slab-use-after-free in gfs2_qd_dealloc
• CVE-url: https://ubuntu.com/security/CVE-2023-52629
  • sh: push-switch: Reorder cleanup operations to avoid use-after-free bug
• CVE-url: https://ubuntu.com/security/CVE-2024-39484
  • mmc: davinci: Don't strip remove function when driver is builtin
• Miscellaneous upstream changes
  • fixup! blk-mq: fix IO hang from sbitmap wakeup race
  • fixup! scsi: qla2xxx: Fix double free of fcport

• CVE-url: https://ubuntu.com/security/CVE-2024-26752
  • l2tp: pass correct message length to ip6_append_data
• CVE-url: https://ubuntu.com/security/CVE-2021-47188
  • scsi: ufs: core: Improve SCSI abort handling
• CVE-url: https://ubuntu.com/security/CVE-2024-26677
  • rxrpc: Fix delayed ACKs to not set the reference serial number
• CVE-url: https://ubuntu.com/security/CVE-2023-52527
  • ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()
• CVE-url: https://ubuntu.com/security/CVE-2024-43882
  • exec: Fix ToCToU between perm check and set-uid/gid usage
• CVE-url: https://ubuntu.com/security/CVE-2022-48943
  • KVM: x86/mmu: make apf token non-zero to fix bug
• CVE-url: https://ubuntu.com/security/CVE-2024-38630
  • watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger
• CVE-url: https://ubuntu.com/security/CVE-2024-44987
  • ipv6: prevent UAF in ip6_send_skb()
• CVE-url: https://ubuntu.com/security/CVE-2024-42285
  • RDMA/iwcm: Fix a use-after-free related to destroying CM IDs
• CVE-url: https://ubuntu.com/security/CVE-2022-48733
  • btrfs: fix use-after-free after failure to create a snapshot
• CVE-url: https://ubuntu.com/security/CVE-2024-44940
  • fou: remove warn in gue_gro_receive on unsupported protocol
• CVE-url: https://ubuntu.com/security/CVE-2024-41059
  • hfsplus: fix uninit-value in copy_name
• CVE-url: https://ubuntu.com/security/CVE-2024-46673
  • scsi: aacraid: Fix double-free on probe failure
• CVE-url: https://ubuntu.com/security/CVE-2024-42313
  • media: venus: fix use after free in vdec_close
• CVE-url: https://ubuntu.com/security/CVE-2024-44999
  • gtp: pull network headers in gtp_dev_xmit()
• CVE-url: https://ubuntu.com/security/CVE-2024-42271
  • net/iucv: fix use after free in iucv_sock_close()
• CVE-url: https://ubuntu.com/security/CVE-2024-44942
  • f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC
• CVE-url: https://ubuntu.com/security/CVE-2024-43858
  • jfs: Fix array-index-out-of-bounds in diFree
• CVE-url: https://ubuntu.com/security/CVE-2024-41071
  • wifi: mac80211: Avoid address calculations via out of bounds array indexing
• CVE-url: https://ubuntu.com/security/CVE-2024-42301
  • dev/parport: fix the array out-of-bounds risk
• CVE-url: https://ubuntu.com/security/CVE-2024-46674
  • usb: dwc3: st: fix probed platform device ref count on probe error path
• CVE-url: https://ubuntu.com/security/CVE-2024-43900
  • media: xc2028: avoid use-after-free in load_firmware_cb()
• CVE-url: https://ubuntu.com/security/CVE-2024-42284
  • tipc: Return non-zero value from tipc_udp_addr2str() on error
• CVE-url: https://ubuntu.com/security/CVE-2024-44998
  • atm: idt77252: prevent use after free in dequeue_rx()
• CVE-url: https://ubuntu.com/security/CVE-2024-42280
  • mISDN: Fix a use after free in hfcmulti_tx()
• CVE-url: https://ubuntu.com/security/CVE-2024-39503
  • netns: add pre_exit method to struct pernet_operations
  • netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type
• CVE-url: https://ubuntu.com/security/CVE-2024-39499
  • vmci: prevent speculation leaks by sanitizing event in event_deliver()
• CVE-url: https://ubuntu.com/security/CVE-2024-40988
  • drm/radeon: fix UBSAN warning in kv_dpm.c
• CVE-url: https://ubuntu.com/security/CVE-2024-40916
  • drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found
• CVE-url: https://ubuntu.com/security/CVE-2024-40904
  • USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages
• CVE-url: https://ubuntu.com/security/CVE-2024-39506
  • liquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet
• CVE-url: https://ubuntu.com/security/CVE-2024-42106
  • inet_diag: Initialize pad field in struct inet_diag_req_v2
• CVE-url:…

[ Ubuntu: 4.15.0-237.248 ]

• CVE-url: https://ubuntu.com/security/CVE-2024-26752
  • l2tp: pass correct message length to ip6_append_data
• CVE-url: https://ubuntu.com/security/CVE-2021-47188
  • scsi: ufs: core: Improve SCSI abort handling
• CVE-url: https://ubuntu.com/security/CVE-2024-26677
  • rxrpc: Fix delayed ACKs to not set the reference serial number
• CVE-url: https://ubuntu.com/security/CVE-2023-52527
  • ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()
• CVE-url: https://ubuntu.com/security/CVE-2024-43882
  • exec: Fix ToCToU between perm check and set-uid/gid usage
• CVE-url: https://ubuntu.com/security/CVE-2022-48943
  • KVM: x86/mmu: make apf token non-zero to fix bug
• CVE-url: https://ubuntu.com/security/CVE-2024-38630
  • watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger
• CVE-url: https://ubuntu.com/security/CVE-2024-44987
  • ipv6: prevent UAF in ip6_send_skb()
• CVE-url: https://ubuntu.com/security/CVE-2024-42285
  • RDMA/iwcm: Fix a use-after-free related to destroying CM IDs
• CVE-url: https://ubuntu.com/security/CVE-2022-48733
  • btrfs: fix use-after-free after failure to create a snapshot
• CVE-url: https://ubuntu.com/security/CVE-2024-44940
  • fou: remove warn in gue_gro_receive on unsupported protocol
• CVE-url: https://ubuntu.com/security/CVE-2024-41059
  • hfsplus: fix uninit-value in copy_name
• CVE-url: https://ubuntu.com/security/CVE-2024-46673
  • scsi: aacraid: Fix double-free on probe failure
• CVE-url: https://ubuntu.com/security/CVE-2024-42313
  • media: venus: fix use after free in vdec_close
• CVE-url: https://ubuntu.com/security/CVE-2024-44999
  • gtp: pull network headers in gtp_dev_xmit()
• CVE-url: https://ubuntu.com/security/CVE-2024-42271
  • net/iucv: fix use after free in iucv_sock_close()
• CVE-url: https://ubuntu.com/security/CVE-2024-44942
  • f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC
• CVE-url: https://ubuntu.com/security/CVE-2024-43858
  • jfs: Fix array-index-out-of-bounds in diFree
• CVE-url: https://ubuntu.com/security/CVE-2024-41071
  • wifi: mac80211: Avoid address calculations via out of bounds array indexing
• CVE-url: https://ubuntu.com/security/CVE-2024-42301
  • dev/parport: fix the array out-of-bounds risk
• CVE-url: https://ubuntu.com/security/CVE-2024-46674
  • usb: dwc3: st: fix probed platform device ref count on probe error path
• CVE-url: https://ubuntu.com/security/CVE-2024-43900
  • media: xc2028: avoid use-after-free in load_firmware_cb()
• CVE-url: https://ubuntu.com/security/CVE-2024-42284
  • tipc: Return non-zero value from tipc_udp_addr2str() on error
• CVE-url: https://ubuntu.com/security/CVE-2024-44998
  • atm: idt77252: prevent use after free in dequeue_rx()
• CVE-url: https://ubuntu.com/security/CVE-2024-42280
  • mISDN: Fix a use after free in hfcmulti_tx()
• CVE-url: https://ubuntu.com/security/CVE-2024-39503
  • netns: add pre_exit method to struct pernet_operations
  • netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type
• CVE-url: https://ubuntu.com/security/CVE-2024-39499
  • vmci: prevent speculation leaks by sanitizing event in event_deliver()
• CVE-url: https://ubuntu.com/security/CVE-2024-40988
  • drm/radeon: fix UBSAN warning in kv_dpm.c
• CVE-url: https://ubuntu.com/security/CVE-2024-40916
  • drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found
• CVE-url: https://ubuntu.com/security/CVE-2024-40904
  • USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages
• CVE-url: https://ubuntu.com/security/CVE-2024-39506
  • liquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet
• CVE-url: https://ubuntu.com/security/CVE-2024-42106
  • inet_diag: Initialize pad field in struct inet_diag_req_v2 …

• CVE-url: https://ubuntu.com/security/CVE-2024-26752
  • l2tp: pass correct message length to ip6_append_data
• CVE-url: https://ubuntu.com/security/CVE-2021-47188
  • scsi: ufs: core: Improve SCSI abort handling
• CVE-url: https://ubuntu.com/security/CVE-2024-26677
  • rxrpc: Fix delayed ACKs to not set the reference serial number
• CVE-url: https://ubuntu.com/security/CVE-2023-52527
  • ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()
• CVE-url: https://ubuntu.com/security/CVE-2024-43882
  • exec: Fix ToCToU between perm check and set-uid/gid usage
• CVE-url: https://ubuntu.com/security/CVE-2022-48943
  • KVM: x86/mmu: make apf token non-zero to fix bug
• CVE-url: https://ubuntu.com/security/CVE-2024-38630
  • watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger
• CVE-url: https://ubuntu.com/security/CVE-2024-44987
  • ipv6: prevent UAF in ip6_send_skb()
• CVE-url: https://ubuntu.com/security/CVE-2024-42285
  • RDMA/iwcm: Fix a use-after-free related to destroying CM IDs
• CVE-url: https://ubuntu.com/security/CVE-2022-48733
  • btrfs: fix use-after-free after failure to create a snapshot
• CVE-url: https://ubuntu.com/security/CVE-2024-44940
  • fou: remove warn in gue_gro_receive on unsupported protocol
• CVE-url: https://ubuntu.com/security/CVE-2024-41059
  • hfsplus: fix uninit-value in copy_name
• CVE-url: https://ubuntu.com/security/CVE-2024-46673
  • scsi: aacraid: Fix double-free on probe failure
• CVE-url: https://ubuntu.com/security/CVE-2024-42313
  • media: venus: fix use after free in vdec_close
• CVE-url: https://ubuntu.com/security/CVE-2024-44999
  • gtp: pull network headers in gtp_dev_xmit()
• CVE-url: https://ubuntu.com/security/CVE-2024-42271
  • net/iucv: fix use after free in iucv_sock_close()
• CVE-url: https://ubuntu.com/security/CVE-2024-44942
  • f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC
• CVE-url: https://ubuntu.com/security/CVE-2024-43858
  • jfs: Fix array-index-out-of-bounds in diFree
• CVE-url: https://ubuntu.com/security/CVE-2024-41071
  • wifi: mac80211: Avoid address calculations via out of bounds array indexing
• CVE-url: https://ubuntu.com/security/CVE-2024-42301
  • dev/parport: fix the array out-of-bounds risk
• CVE-url: https://ubuntu.com/security/CVE-2024-46674
  • usb: dwc3: st: fix probed platform device ref count on probe error path
• CVE-url: https://ubuntu.com/security/CVE-2024-43900
  • media: xc2028: avoid use-after-free in load_firmware_cb()
• CVE-url: https://ubuntu.com/security/CVE-2024-42284
  • tipc: Return non-zero value from tipc_udp_addr2str() on error
• CVE-url: https://ubuntu.com/security/CVE-2024-44998
  • atm: idt77252: prevent use after free in dequeue_rx()
• CVE-url: https://ubuntu.com/security/CVE-2024-42280
  • mISDN: Fix a use after free in hfcmulti_tx()
• CVE-url: https://ubuntu.com/security/CVE-2024-39503
  • netns: add pre_exit method to struct pernet_operations
  • netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type
• CVE-url: https://ubuntu.com/security/CVE-2024-39499
  • vmci: prevent speculation leaks by sanitizing event in event_deliver()
• CVE-url: https://ubuntu.com/security/CVE-2024-40988
  • drm/radeon: fix UBSAN warning in kv_dpm.c
• CVE-url: https://ubuntu.com/security/CVE-2024-40916
  • drm/exynos: hdmi: report safe 640x480 mode as a fallback when no EDID found
• CVE-url: https://ubuntu.com/security/CVE-2024-40904
  • USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages
• CVE-url: https://ubuntu.com/security/CVE-2024-39506
  • liquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet
• CVE-url: https://ubuntu.com/security/CVE-2024-42106
  • inet_diag: Initialize pad field in struct inet_diag_req_v2
• CVE-url:…

Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux Kernel contained a race condition, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-22099)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• GPU drivers;
• MMC subsystem;
• Network drivers;
• PHY drivers;
• Pin controllers subsystem;
• Xen hypervisor drivers;
• GFS2 file system;
• Core kernel;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• HD-audio driver;
• ALSA SH drivers; (CVE-2024-26903, CVE-2024-35835, CVE-2023-52644, CVE-2024-39292, CVE-2024-36940, CVE-2024-26600, CVE-2023-52629, CVE-2024-35955, CVE-2023-52760, CVE-2023-52806, CVE-2024-39484, CVE-2024-26679, CVE-2024-26654, CVE-2024-36901, CVE-2024-26687, CVE-2023-52470)

Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux Kernel contained a race condition, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-22099)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• GPU drivers;
• MMC subsystem;
• Network drivers;
• PHY drivers;
• Pin controllers subsystem;
• Xen hypervisor drivers;
• GFS2 file system;
• Core kernel;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• HD-audio driver;
• ALSA SH drivers; (CVE-2024-26903, CVE-2024-35835, CVE-2023-52644, CVE-2024-39292, CVE-2024-36940, CVE-2024-26600, CVE-2023-52629, CVE-2024-35955, CVE-2023-52760, CVE-2023-52806, CVE-2024-39484, CVE-2024-26679, CVE-2024-26654, CVE-2024-36901, CVE-2024-26687, CVE-2023-52470)

Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux Kernel contained a race condition, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-22099)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• GPU drivers;
• MMC subsystem;
• Network drivers;
• PHY drivers;
• Pin controllers subsystem;
• Xen hypervisor drivers;
• GFS2 file system;
• Core kernel;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• HD-audio driver;
• ALSA SH drivers; (CVE-2024-26903, CVE-2024-35835, CVE-2023-52644, CVE-2024-39292, CVE-2024-36940, CVE-2024-26600, CVE-2023-52629, CVE-2024-35955, CVE-2023-52760, CVE-2023-52806, CVE-2024-39484, CVE-2024-26679, CVE-2024-26654, CVE-2024-36901, CVE-2024-26687, CVE-2023-52470)

Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux Kernel contained a race condition, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-22099)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• GPU drivers;
• MMC subsystem;
• Network drivers;
• PHY drivers;
• Pin controllers subsystem;
• Xen hypervisor drivers;
• GFS2 file system;
• Core kernel;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• HD-audio driver;
• ALSA SH drivers; (CVE-2024-26903, CVE-2024-35835, CVE-2023-52644, CVE-2024-39292, CVE-2024-36940, CVE-2024-26600, CVE-2023-52629, CVE-2024-35955, CVE-2023-52760, CVE-2023-52806, CVE-2024-39484, CVE-2024-26679, CVE-2024-26654, CVE-2024-36901, CVE-2024-26687, CVE-2023-52470)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• SuperH RISC architecture;
• MMC subsystem;
• Network drivers;
• SCSI drivers;
• GFS2 file system;
• IPv4 networking;
• IPv6 networking;
• HD-audio driver; (CVE-2024-26830, CVE-2024-39484, CVE-2024-36901, CVE-2024-26929, CVE-2024-26921, CVE-2021-46926, CVE-2023-52629, CVE-2023-52760)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• SuperH RISC architecture;
• MMC subsystem;
• Network drivers;
• SCSI drivers;
• GFS2 file system;
• IPv4 networking;
• IPv6 networking;
• HD-audio driver; (CVE-2024-26830, CVE-2024-39484, CVE-2024-36901, CVE-2024-26929, CVE-2024-26921, CVE-2021-46926, CVE-2023-52629, CVE-2023-52760)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• SuperH RISC architecture;
• MMC subsystem;
• Network drivers;
• SCSI drivers;
• GFS2 file system;
• IPv4 networking;
• IPv6 networking;
• HD-audio driver; (CVE-2024-26830, CVE-2024-39484, CVE-2024-36901, CVE-2024-26929, CVE-2024-26921, CVE-2021-46926, CVE-2023-52629, CVE-2023-52760)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• SuperH RISC architecture;
• MMC subsystem;
• Network drivers;
• SCSI drivers;
• GFS2 file system;
• IPv4 networking;
• IPv6 networking;
• HD-audio driver; (CVE-2024-26830, CVE-2024-39484, CVE-2024-36901, CVE-2024-26929, CVE-2024-26921, CVE-2021-46926, CVE-2023-52629, CVE-2023-52760)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• MMC subsystem;
• Network drivers;
• GFS2 file system;
• IPv4 networking;
• IPv6 networking; (CVE-2024-26921, CVE-2023-52629, CVE-2024-26680, CVE-2024-26830, CVE-2024-39484, CVE-2024-39292, CVE-2024-36901, CVE-2023-52760)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• MMC subsystem;
• Network drivers;
• GFS2 file system;
• IPv4 networking;
• IPv6 networking; (CVE-2024-26921, CVE-2023-52629, CVE-2024-26680, CVE-2024-26830, CVE-2024-39484, CVE-2024-39292, CVE-2024-36901, CVE-2023-52760)

Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux Kernel contained a race condition, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-22099)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• SuperH RISC architecture;
• User-Mode Linux (UML);
• GPU drivers;
• HID subsystem;
• MMC subsystem;
• Network drivers;
• PHY drivers;
• SCSI drivers;
• USB subsystem;
• Xen hypervisor drivers;
• GFS2 file system;
• Memory management;
• Bluetooth subsystem;
• IPv4 networking;
• IPv6 networking;
• NFC subsystem;
• HD-audio driver;
• ALSA SH drivers; (CVE-2023-52806, CVE-2021-46924, CVE-2021-47521, CVE-2021-47542, CVE-2024-26903, CVE-2024-26654, CVE-2024-27013, CVE-2024-26600, CVE-2021-47518, CVE-2021-47171, CVE-2023-52629, CVE-2023-52644, CVE-2021-46904, CVE-2023-52470, CVE-2024-36901, CVE-2021-46906, CVE-2024-39292, CVE-2022-48659, CVE-2021-47173, CVE-2021-47571, CVE-2024-26929, CVE-2024-39484, CVE-2024-26687, CVE-2024-26679, CVE-2023-52760)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel, leading to a null pointer dereference vulnerability. A privileged local attacker could use this to possibly cause a denial of service (system crash). (CVE-2024-24860)

It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• MIPS architecture;
• PowerPC architecture;
• SuperH RISC architecture;
• x86 architecture;
• ACPI drivers;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• GPIO subsystem;
• GPU drivers;
• Greybus drivers;
• HID subsystem;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Media drivers;
• VMware VMCI Driver;
• MMC subsystem;
• Network drivers;
• Pin controllers subsystem;
• S/390 drivers;
• SCSI drivers;
• USB subsystem;
• GFS2 file system;
• JFFS2 file system;
• JFS file system;
• File systems infrastructure;
• NILFS2 file system;
• IOMMU subsystem;
• Sun RPC protocol;
• Netfilter;
• Memory management;
• B.A.T.M.A.N. meshing protocol;
• CAN network layer;
• Ceph Core library;
• Networking core;
• IPv4 networking;
• IPv6 networking;
• IUCV driver;
• MAC80211 subsystem;
• NET/ROM layer;
• Network traffic control;
• HD-audio driver;
• SoC Audio for Freescale CPUs drivers; (CVE-2024-42154, CVE-2024-42093, CVE-2024-42096, CVE-2024-40984, CVE-2024-39502, CVE-2024-36901, CVE-2024-41044, CVE-2024-40961, CVE-2024-40981, CVE-2024-42236, CVE-2024-42232, CVE-2024-41041, CVE-2024-40958, CVE-2024-40905, CVE-2024-42084, CVE-2024-40934, CVE-2024-42124, CVE-2024-39505, CVE-2024-39506, CVE-2024-39501, CVE-2021-46926, CVE-2024-40941, CVE-2024-42145, CVE-2024-41089, CVE-2024-40932, CVE-2024-42224, CVE-2024-41097, CVE-2024-40959, CVE-2024-42157, CVE-2024-39469, CVE-2024-39499, CVE-2024-40974, CVE-2024-42094, CVE-2024-36894, CVE-2024-42087, CVE-2024-42104, CVE-2023-52803, CVE-2024-41034, CVE-2024-40995, CVE-2023-52629, CVE-2024-40912, CVE-2024-39484, CVE-2024-41006, CVE-2023-52760, CVE-2024-41095, CVE-2024-41046, CVE-2024-42070, CVE-2023-52887, CVE-2024-40960, CVE-2024-41007, CVE-2024-40901, CVE-2024-42119, CVE-2024-40987, CVE-2024-42148, CVE-2024-41049, CVE-2024-40963, CVE-2024-41087, CVE-2024-42223, CVE-2024-42090, CVE-2024-42105, CVE-2024-42089, CVE-2024-40916, CVE-2024-40942, CVE-2024-40978, CVE-2024-40902, CVE-2024-26921, CVE-2024-39495, CVE-2024-40943, CVE-2024-36978, CVE-2024-26929, CVE-2024-40988, CVE-2024-39503, CVE-2024-42101, CVE-2024-40904, CVE-2024-42086, CVE-2024-42106, CVE-2024-26830, CVE-2024-41035, CVE-2024-42153, CVE-2024-39509, CVE-2024-37078, CVE-2024-42076, CVE-2024-36974, CVE-2024-40980, CVE-2024-40945, CVE-2024-39487, CVE-2024-42092, CVE-2024-38619, CVE-2024-42127, CVE-2024-40968, CVE-2024-42115, CVE-2024-42102, CVE-2024-42097)

Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not properly handle certain error conditions, leading to a NULL pointer dereference. A local attacker could possibly trigger this vulnerability to cause a denial of service. (CVE-2022-38096)

Gui-Dong Han discovered that the software RAID driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. A privileged attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-23307)

Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2024-23848)

It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel when modifying certain settings values through debugfs. A privileged local attacker could use this to cause a denial of service. (CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)

Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in the Linux kernel contained a race condition, leading to an integer overflow vulnerability. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-24861)

Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device volume management subsystem did not properly validate logical eraseblock sizes in certain situations. An attacker could possibly use this to cause a denial of service (system crash). (CVE-2024-25739)

Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the device to be enabled before writing. A local attacker could possibly use this to cause a denial of service. (CVE-2024-25741)

Benedict Schlüter, Supraja Sridhara, Andrin Bertschi, and Shweta Shinde discovered that an untrusted hypervisor could inject malicious #VC interrupts and compromise the security guarantees of AMD SEV-SNP. This flaw is known as WeSee. A local attacker in control of the hypervisor could use this to expose sensitive information or possibly execute arbitrary code in the trusted execution environment. (CVE-2024-25742)

It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing xattr debug information. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-40902)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• ARM32 architecture;
• ARM64 architecture;
• M68K architecture;
• MIPS architecture;
• PowerPC architecture;
• RISC-V architecture;
• SuperH RISC architecture;
• User-Mode Linux (UML);
• x86 architecture;
• Block layer subsystem;
• Cryptographic API;
• Accessibility subsystem;
• ACPI drivers;
• Android drivers;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Bluetooth drivers;
• Character device driver;
• Clock framework and drivers;
• Data acquisition framework and drivers;
• CPU frequency scaling framework;
• Hardware crypto device drivers;
• Buffer Sharing and Synchronization framework;
• DMA engine subsystem;
• FireWire subsystem;
• FPGA Framework;
• GPIO subsystem;
• GPU drivers;
• Greybus drivers;
• HID subsystem;
• HW tracing;
• I2C subsystem;
• IIO subsystem;
• InfiniBand drivers;
• Input Device (Mouse) drivers;
• IRQ chip drivers;
• Macintosh device drivers;
• Multiple devices driver;
• Media drivers;
• EEPROM drivers;
• VMware VMCI Driver;
• MMC subsystem;
• Network drivers;
• Near Field Communication (NFC) drivers;
• NVME drivers;
• Device tree and open firmware driver;
• PCI subsystem;
• Pin controllers subsystem;
• PTP clock framework;
• Remote Processor subsystem;
• S/390 drivers;
• SCSI drivers;
• Freescale SoC…