CVE-2025-40271

In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix uaf in proc_readdir_de() Pde is erased from subdir rbtree through rb_erase(), but not set the node to EMPTY, which may result in uaf access. We should use RB_CLEAR_NODE() set the erased node to EMPTY, then pde_subdir_next() will return NULL to avoid uaf access. We found an uaf issue while using stress-ng testing, need to run testcase getdent and tun in the same time. The steps of the issue is as follows: 1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current pde is tun3; 2) in the [time windows] unregister netdevice tun3 and tun2, and erase them from rbtree. erase tun3 first, and then erase tun2. the pde(tun2) will be released to slab; 3) continue to getdent process, then pde_subdir_next() will return pde(tun2) which is released, it will case uaf access. CPU 0 | CPU 1 ------------------------------------------------------------------------- traverse dir /proc/pid/net/dev_snmp6/ | unregister_netdevice(tun->dev) //tun3 tun2 sys_getdents64() | iterate_dir() | proc_readdir() | proc_readdir_de() | snmp6_unregister_dev() pde_get(de); | proc_remove() read_unlock(&proc_subdir_lock); | remove_proc_subtree() | write_lock(&proc_subdir_lock); [time window] | rb_erase(&root->subdir_node, &parent->subdir); | write_unlock(&proc_subdir_lock); read_lock(&proc_subdir_lock); | next = pde_subdir_next(de); | pde_put(de); | de = next; //UAF | rbtree of dev_snmp6 | pde(tun3) / \ NULL pde(tun2)

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

cacheinfo: Fix shared_cpu_map to handle shared caches at different levels

The cacheinfo sets up the shared_cpu_map by checking whether the caches with the same index are shared between CPUs. However, this will trigger slab-out-of-bounds access if the CPUs do not have the same cache hierarchy. Another problem is the mismatched shared_cpu_map when the shared cache does not have the same index between CPUs.

CPU0 I D L3 index 0 1 2 x ^ ^ ^ ^ index 0 1 2 3 CPU1 I D L2 L3

This patch checks each cache is shared with all caches on other CPUs.(CVE-2023-53254)

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

drm/radeon: Fix integer overflow in radeon_cs_parser_init

The type of size is unsigned, if size is 0x40000000, there will be an integer overflow, size will be zero after size *= sizeof(uint32_t), will cause uninitialized memory to be referenced later(CVE-2023-53309)

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

media: v4l2-mem2mem: add lock to protect parameter num_rdy

Getting below error when using KCSAN to check the driver. Adding lock to protect parameter num_rdy when getting the value with function: v4l2_m2m_num_src_bufs_ready/v4l2_m2m_num_dst_bufs_ready.

kworker/u16:3: [name:report&]BUG: KCSAN: data-race in v4l2_m2m_buf_queue kworker/u16:3: [name:report&]

kworker/u16:3: [name:report&]read-write to 0xffffff8105f35b94 of 1 bytes by task 20865 on cpu 7: kworker/u16:3:  v4l2_m2m_buf_queue+0xd8/0x10c(CVE-2023-53519)

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

wifi: brcmfmac: cfg80211: Pass the PMK in binary instead of hex

Apparently the hex passphrase mechanism does not work on newer chips/firmware (e.g. BCM4387). It seems there was a simple way of passing it in binary all along, so use that and avoid the hexification.

OpenBSD has been doing it like this from the beginning, so this should work on all chips.

Also clear the structure before setting the PMK. This was leaking uninitialized stack contents to the device.(CVE-2023-53715)

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

usb-storage: alauda: Fix uninit-value in alauda_check_media()

Syzbot got KMSAN to complain about access to an uninitialized value in the alauda subdriver of usb-storage:

BUG: KMSAN: uninit-value in alauda_transport+0x462/0x57f0 drivers/usb/storage/alauda.c:1137 CPU: 0 PID: 12279 Comm: usb-storage Not tainted 5.3.0-rc7+ #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x191/0x1f0 lib/dump_stack.c:113 kmsan_report+0x13a/0x2b0 mm/kmsan/kmsan_report.c:108 __msan_warning+0x73/0xe0 mm/kmsan/kmsan_instr.c:250 alauda_check_media+0x344/0x3310 drivers/usb/storage/alauda.c:460

The problem is that alauda_check_media() doesn't verify that its USB transfer succeeded before trying to use the received data. What should happen if the transfer fails isn't entirely clear, but a reasonably conservative approach is to pretend that no media is present.

A similar problem exists in a usb_stor_dbg() call in alauda_get_media_status(). In this case, when an error occurs the call is redundant, because usb_stor_ctrl_transfer() already will print a debugging message.

Finally, unrelated to the uninitialized memory access, is the fact that alauda_check_media() performs DMA to a buffer on the stack. Fortunately usb-storage provides a general purpose DMA-able buffer for uses like this. We'll use it instead.(CVE-2023-53847)

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

RDMA/mlx4: Prevent shift wrapping in set_user_sq_size()

The ucmd->log_sq_bb_count variable is controlled by the user so this shift can wrap. Fix it by using check_shl_overflow() in the same way that it…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:kernel/resource: fix kfree() of bootmem memory againSince commit ebff7d8f270d ( mem hotunplug: fix kfree() of bootmemmemory ), we could get a resource allocated during boot viaalloc_resource(). And it s required to release the resource usingfree_resource(). Howerver, many people use kfree directly which willresult in kernel BUG. In order to fix this without fixing every callsite, just leak a couple of bytes in such corner case.(CVE-2022-49190)

In the Linux kernel, the following vulnerability has been resolved:drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback()There is a deadlock in rtw_surveydone_event_callback(),which is shown below: (Thread 1) | (Thread 2) | _set_timer()rtw_surveydone_event_callback()| mod_timer() spin_lock_bh() //(1) | (wait a time) ... | rtw_scan_timeout_handler() del_timer_sync() | spin_lock_bh() //(2) (wait timer to stop) | ...We hold pmlmepriv->lock in position (1) of thread 1 and usedel_timer_sync() to wait timer to stop, but timer handleralso need pmlmepriv->lock in position (2) of thread 2.As a result, rtw_surveydone_event_callback() will block forever.This patch extracts del_timer_sync() from the protection ofspin_lock_bh(), which could let timer handler to obtainthe needed lock. What`s more, we change spin_lock_bh() inrtw_scan_timeout_handler() to spin_lock_irq(). Otherwise,spin_lock_bh() will also cause deadlock() in timer handler.(CVE-2022-49309)

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

drm/scheduler: fix fence ref counting

We leaked dependency fences when processes were beeing killed.

Additional to that grab a reference to the last scheduled fence.(CVE-2022-49829)

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

usb: cdns3: fix random warning message when driver load

Warning log: [ 4.141392] Unexpected gfp: 0x4 (GFP_DMA32). Fixing up to gfp: 0xa20 (GFP_ATOMIC). Fix your code! [ 4.150340] CPU: 1 PID: 175 Comm: 1-0050 Not tainted 5.15.5-00039-g2fd9ae1b568c #20 [ 4.158010] Hardware name: Freescale i.MX8QXP MEK (DT) [ 4.163155] Call trace: [ 4.165600] dump_backtrace+0x0/0x1b0 [ 4.169286] show_stack+0x18/0x68 [ 4.172611] dump_stack_lvl+0x68/0x84 [ 4.176286] dump_stack+0x18/0x34 [ 4.179613] kmalloc_fix_flags+0x60/0x88 [ 4.183550] new_slab+0x334/0x370 [ 4.186878] ___slab_alloc.part.108+0x4d4/0x748 [ 4.191419] __slab_alloc.isra.109+0x30/0x78 [ 4.195702] kmem_cache_alloc+0x40c/0x420 [ 4.199725] dma_pool_alloc+0xac/0x1f8 [ 4.203486] cdns3_allocate_trb_pool+0xb4/0xd0

pool_alloc_page(struct dma_pool *pool, gfp_t mem_flags) { ... page = kmalloc(sizeof(*page), mem_flags); page->vaddr = dma_alloc_coherent(pool->dev, pool->allocation, &page->dma, mem_flags); ... }

kmalloc was called with mem_flags, which is passed down in cdns3_allocate_trb_pool() and have GFP_DMA32 flags. kmall_fix_flags() report warning.

GFP_DMA32 is not useful at all. dma_alloc_coherent() will handle DMA memory region correctly by pool->dev. GFP_DMA32 can be removed safely.(CVE-2022-50151)

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

of: check previous kernel's ima-kexec-buffer against memory bounds

Presently ima_get_kexec_buffer() doesn't check if the previous kernel's ima-kexec-buffer lies outside the addressable memory range. This can result in a kernel panic if the new kernel is booted with 'mem=X' arg and the ima-kexec-buffer was allocated beyond that range by the previous kernel. The panic is usually of the form below:

$ sudo kexec --initrd initrd vmlinux --append='mem=16G'

<snip> BUG: Unable to handle kernel data access on read at…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

iommu/s390: Implement blocking domain

This fixes a crash when surprise hot-unplugging a PCI device. This crash happens because during hot-unplug __iommu_group_set_domain_nofail() attaching the default domain fails when the platform no longer recognizes the device as it has already been removed and we end up with a NULL domain pointer and UAF. This is exactly the case referred to in the second comment in __iommu_device_set_domain() and just as stated there if we can instead attach the blocking domain the UAF is prevented as this can handle the already removed device. Implement the blocking domain to use this handling. With this change, the crash is fixed but we still hit a warning attempting to change DMA ownership on a blocked device.(CVE-2024-53232)

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

iommu: Fix two issues in iommu_copy_struct_from_user()

In the review for iommu_copy_struct_to_user() helper, Matt pointed out that a NULL pointer should be rejected prior to dereferencing it: https://lore.kernel.org/all/(CVE-2025-37900)

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

smb: client: Avoid race in open_cached_dir with lease breaks

A pre-existing valid cfid returned from find_or_create_cached_dir might race with a lease break, meaning open_cached_dir doesn't consider it valid, and thinks it's newly-constructed. This leaks a dentry reference if the allocation occurs before the queued lease break work runs.

Avoid the race by extending holding the cfid_list_lock across find_or_create_cached_dir and when the result is checked.(CVE-2025-37954)

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

net_sched: prio: fix a race in prio_tune()

Gerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer fires at the wrong time.

The race is as follows:

CPU 0 CPU 1 [1]: lock root [2]: qdisc_tree_flush_backlog() [3]: unlock root | | [5]: lock root | [6]: rehash | [7]: qdisc_tree_reduce_backlog() | [4]: qdisc_put()

This can be abused to underflow a parent's qlen.

Calling qdisc_purge_queue() instead of qdisc_tree_flush_backlog() should fix the race, because all packets will be purged from the qdisc before releasing the lock.(CVE-2025-38083)

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

IB/mlx5: Fix potential deadlock in MR deregistration

The issue arises when kzalloc() is invoked while holding umem_mutex or any other lock acquired under umem_mutex. This is problematic because kzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke mmu_notifier_invalidate_range_start(). This function can lead to mlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again, resulting in a deadlock.

The problematic flow: CPU0 | CPU1 ---------------------------------------|------------------------------------------------ mlx5_ib_dereg_mr() | → revoke_mr() | → mutex_lock(&umem_odp->umem_mutex) | | mlx5_mkey_cache_init() | → mutex_lock(&dev->cache.rb_lock) | → mlx5r_cache_create_ent_locked() | → kzalloc(GFP_KERNEL) | → fs_reclaim() | → mmu_notifier_invalidate_range_start() | → mlx5_ib_invalidate_range() | → mutex_lock(&umem_odp->umem_mutex) →…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

iommu/s390: Implement blocking domain

This fixes a crash when surprise hot-unplugging a PCI device. This crash happens because during hot-unplug __iommu_group_set_domain_nofail() attaching the default domain fails when the platform no longer recognizes the device as it has already been removed and we end up with a NULL domain pointer and UAF. This is exactly the case referred to in the second comment in __iommu_device_set_domain() and just as stated there if we can instead attach the blocking domain the UAF is prevented as this can handle the already removed device. Implement the blocking domain to use this handling. With this change, the crash is fixed but we still hit a warning attempting to change DMA ownership on a blocked device.(CVE-2024-53232)

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

iommu: Fix two issues in iommu_copy_struct_from_user()

In the review for iommu_copy_struct_to_user() helper, Matt pointed out that a NULL pointer should be rejected prior to dereferencing it: https://lore.kernel.org/all/(CVE-2025-37900)

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

smb: client: Avoid race in open_cached_dir with lease breaks

A pre-existing valid cfid returned from find_or_create_cached_dir might race with a lease break, meaning open_cached_dir doesn't consider it valid, and thinks it's newly-constructed. This leaks a dentry reference if the allocation occurs before the queued lease break work runs.

Avoid the race by extending holding the cfid_list_lock across find_or_create_cached_dir and when the result is checked.(CVE-2025-37954)

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

net_sched: prio: fix a race in prio_tune()

Gerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer fires at the wrong time.

The race is as follows:

CPU 0 CPU 1 [1]: lock root [2]: qdisc_tree_flush_backlog() [3]: unlock root | | [5]: lock root | [6]: rehash | [7]: qdisc_tree_reduce_backlog() | [4]: qdisc_put()

This can be abused to underflow a parent's qlen.

Calling qdisc_purge_queue() instead of qdisc_tree_flush_backlog() should fix the race, because all packets will be purged from the qdisc before releasing the lock.(CVE-2025-38083)

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

IB/mlx5: Fix potential deadlock in MR deregistration

The issue arises when kzalloc() is invoked while holding umem_mutex or any other lock acquired under umem_mutex. This is problematic because kzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke mmu_notifier_invalidate_range_start(). This function can lead to mlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again, resulting in a deadlock.

The problematic flow: CPU0 | CPU1 ---------------------------------------|------------------------------------------------ mlx5_ib_dereg_mr() | → revoke_mr() | → mutex_lock(&umem_odp->umem_mutex) | | mlx5_mkey_cache_init() | → mutex_lock(&dev->cache.rb_lock) | → mlx5r_cache_create_ent_locked() | → kzalloc(GFP_KERNEL) | → fs_reclaim() | → mmu_notifier_invalidate_range_start() | → mlx5_ib_invalidate_range() | → mutex_lock(&umem_odp->umem_mutex) →…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

iommu/s390: Implement blocking domain

This fixes a crash when surprise hot-unplugging a PCI device. This crash happens because during hot-unplug __iommu_group_set_domain_nofail() attaching the default domain fails when the platform no longer recognizes the device as it has already been removed and we end up with a NULL domain pointer and UAF. This is exactly the case referred to in the second comment in __iommu_device_set_domain() and just as stated there if we can instead attach the blocking domain the UAF is prevented as this can handle the already removed device. Implement the blocking domain to use this handling. With this change, the crash is fixed but we still hit a warning attempting to change DMA ownership on a blocked device.(CVE-2024-53232)

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

iommu: Fix two issues in iommu_copy_struct_from_user()

In the review for iommu_copy_struct_to_user() helper, Matt pointed out that a NULL pointer should be rejected prior to dereferencing it: https://lore.kernel.org/all/(CVE-2025-37900)

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

smb: client: Avoid race in open_cached_dir with lease breaks

A pre-existing valid cfid returned from find_or_create_cached_dir might race with a lease break, meaning open_cached_dir doesn't consider it valid, and thinks it's newly-constructed. This leaks a dentry reference if the allocation occurs before the queued lease break work runs.

Avoid the race by extending holding the cfid_list_lock across find_or_create_cached_dir and when the result is checked.(CVE-2025-37954)

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

net_sched: prio: fix a race in prio_tune()

Gerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer fires at the wrong time.

The race is as follows:

CPU 0 CPU 1 [1]: lock root [2]: qdisc_tree_flush_backlog() [3]: unlock root | | [5]: lock root | [6]: rehash | [7]: qdisc_tree_reduce_backlog() | [4]: qdisc_put()

This can be abused to underflow a parent's qlen.

Calling qdisc_purge_queue() instead of qdisc_tree_flush_backlog() should fix the race, because all packets will be purged from the qdisc before releasing the lock.(CVE-2025-38083)

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

IB/mlx5: Fix potential deadlock in MR deregistration

The issue arises when kzalloc() is invoked while holding umem_mutex or any other lock acquired under umem_mutex. This is problematic because kzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke mmu_notifier_invalidate_range_start(). This function can lead to mlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again, resulting in a deadlock.

The problematic flow: CPU0 | CPU1 ---------------------------------------|------------------------------------------------ mlx5_ib_dereg_mr() | → revoke_mr() | → mutex_lock(&umem_odp->umem_mutex) | | mlx5_mkey_cache_init() | → mutex_lock(&dev->cache.rb_lock) | → mlx5r_cache_create_ent_locked() | → kzalloc(GFP_KERNEL) | → fs_reclaim() | → mmu_notifier_invalidate_range_start() | → mlx5_ib_invalidate_range() | → mutex_lock(&umem_odp->umem_mutex) →…

The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.

Security Fix(es):

• kernel: IB/hfi1: Fix sdma.h tx->num_descs off-by-one error (CVE-2024-26766)

• kernel: RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem (CVE-2025-38022)

• kernel: Linux kernel: RDMA/rxe use-after-free vulnerability leading to potential arbitrary code execution (CVE-2025-38024)

• kernel: Linux kernel: Memory corruption in Squashfs due to incorrect block size calculation (CVE-2025-38415)

• kernel: Linux kernel: Denial of Service in ATM CLIP module via infinite recursion (CVE-2025-38459)

• kernel: Linux kernel: Denial of Service via out-of-bounds read in USB configuration parsing (CVE-2025-39760)

• kernel: mptcp: fix race condition in mptcp_schedule_work() (CVE-2025-40258)

• kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. (CVE-2025-40271)

• kernel: Linux kernel: Information disclosure and denial of service via out-of-bounds read in font glyph handling (CVE-2025-40322)

• kernel: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() (CVE-2022-50865)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: IB/hfi1: Fix sdma.h tx->num_descs off-by-one error (CVE-2024-26766)

• kernel: RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem (CVE-2025-38022)

• kernel: Linux kernel: RDMA/rxe use-after-free vulnerability leading to potential arbitrary code execution (CVE-2025-38024)

• kernel: Linux kernel: Memory corruption in Squashfs due to incorrect block size calculation (CVE-2025-38415)

• kernel: Linux kernel: Denial of Service in ATM CLIP module via infinite recursion (CVE-2025-38459)

• kernel: Linux kernel: Denial of Service via out-of-bounds read in USB configuration parsing (CVE-2025-39760)

• kernel: mptcp: fix race condition in mptcp_schedule_work() (CVE-2025-40258)

• kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. (CVE-2025-40271)

• kernel: Linux kernel: Information disclosure and denial of service via out-of-bounds read in font glyph handling (CVE-2025-40322)

• kernel: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() (CVE-2022-50865)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: Linux kernel: irqchip/gic-v2m use-after-free vulnerability (CVE-2025-37819)

• kernel: RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem (CVE-2025-38022)

• kernel: Linux kernel use-after-free in eventpoll (CVE-2025-38349)

• kernel: io_uring/msg_ring: ensure io_kiocb freeing is deferred for RCU (CVE-2025-38453)

• kernel: net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (CVE-2025-38568)

• kernel: drm/xe: Fix vm_bind_ioctl double free bug (CVE-2025-38731)

• kernel: ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (CVE-2025-40154)

• kernel: net: use dst_dev_rcu() in sk_setup_caps() (CVE-2025-40170)

• kernel: ipv6: use RCU in ip6_xmit() (CVE-2025-40135)

• kernel: ipv6: use RCU in ip6_output() (CVE-2025-40158)

• kernel: Linux kernel: vsock vulnerability may lead to memory corruption (CVE-2025-40248)

• kernel: mptcp: fix race condition in mptcp_schedule_work() (CVE-2025-40258)

• kernel: devlink: rate: Unset parent pointer in devl_rate_nodes_destroy (CVE-2025-40251)

• kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. (CVE-2025-40271)

• kernel: Linux kernel: Out-of-bounds write in Bluetooth MGMT can lead to information disclosure and denial of service (CVE-2025-40294)

• kernel: Linux kernel: Information disclosure and denial of service in Bluetooth HCI event handling (CVE-2025-40301)

• kernel: Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once (CVE-2025-40318)

• kernel: net: atlantic: fix fragment overflow handling in RX path (CVE-2025-68301)

• kernel: Bluetooth: hci_sock: Prevent race in socket write iter and sock bind (CVE-2025-68305)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: net: openvswitch: fix nested key length validation in the set() action (CVE-2025-37789)

• kernel: Linux kernel: irqchip/gic-v2m use-after-free vulnerability (CVE-2025-37819)

• kernel: RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem (CVE-2025-38022)

• kernel: Linux kernel: RDMA/rxe use-after-free vulnerability leading to potential arbitrary code execution (CVE-2025-38024)

• kernel: Linux kernel: Memory corruption in Squashfs due to incorrect block size calculation (CVE-2025-38415)

• kernel: vsock/vmci: Clear the vmci transport packet properly when initializing it (CVE-2025-38403)

• kernel: Linux kernel: Denial of Service in ATM CLIP module via infinite recursion (CVE-2025-38459)

• kernel: Linux kernel: Data corruption and system instability due to improper io_uring/net buffer handling (CVE-2025-38730)

• kernel: Linux kernel: Denial of Service via out-of-bounds read in USB configuration parsing (CVE-2025-39760)

• kernel: net: use dst_dev_rcu() in sk_setup_caps() (CVE-2025-40170)

• kernel: ipv6: use RCU in ip6_xmit() (CVE-2025-40135)

• kernel: Bluetooth: ISO: Fix possible UAF on iso_conn_free (CVE-2025-40141)

• kernel: ipv6: use RCU in ip6_output() (CVE-2025-40158)

• kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. (CVE-2025-40271)

• kernel: Linux kernel ALSA USB audio driver: Buffer overflow leading to information disclosure and denial of service (CVE-2025-40269)

• kernel: Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once (CVE-2025-40318)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix uaf in proc_readdir_de() Pde is erased from subdir rbtree through rb_erase(), but not set the node to EMPTY, which may result in uaf access. We should use RB_CLEAR_NODE() set the erased node to EMPTY, then pde_subdir_next() will return NULL to avoid uaf access. We found an uaf issue while using stress-ng testing, need to run testcase getdent and tun in the same time. The steps of the issue is as follows: 1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current pde is tun3; 2) in the [time windows] unregister netdevice tun3 and tun2, and erase them from rbtree. erase tun3 first, and then erase tun2. the pde(tun2) will be released to slab; 3) continue to getdent process, then pde_subdir_next() will return pde(tun2) which is released, it will case uaf access. CPU 0 | CPU 1 ------------------------------------------------------------------------- traverse dir /proc/pid/net/dev_snmp6/ | unregister_netdevice(tun->dev) //tun3 tun2 sys_getdents64() | iterate_dir() | proc_readdir() | proc_readdir_de() | snmp6_unregister_dev() pde_get(de); | proc_remove() read_unlock(&proc_subdir_lock); | remove_proc_subtree() | write_lock(&proc_subdir_lock); [time window] | rb_erase(&root->subdir_node, &parent->subdir); | write_unlock(&proc_subdir_lock); read_lock(&proc_subdir_lock); | next = pde_subdir_next(de); | pde_put(de); | de = next; //UAF | rbtree of dev_snmp6 | pde(tun3) / \ NULL pde(tun2)

The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.

Security Fix(es):

• kernel: IB/hfi1: Fix sdma.h tx->num_descs off-by-one error (CVE-2024-26766)
• kernel: RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem (CVE-2025-38022)
• kernel: Linux kernel: RDMA/rxe use-after-free vulnerability leading to potential arbitrary code execution (CVE-2025-38024)
• kernel: Linux kernel: Memory corruption in Squashfs due to incorrect block size calculation (CVE-2025-38415)
• kernel: Linux kernel: Denial of Service in ATM CLIP module via infinite recursion (CVE-2025-38459)
• kernel: Linux kernel: Denial of Service via out-of-bounds read in USB configuration parsing (CVE-2025-39760)
• kernel: mptcp: fix race condition in mptcp_schedule_work() (CVE-2025-40258)
• kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. (CVE-2025-40271)
• kernel: Linux kernel: Information disclosure and denial of service via out-of-bounds read in font glyph handling (CVE-2025-40322)
• kernel: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() (CVE-2022-50865)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: IB/hfi1: Fix sdma.h tx->num_descs off-by-one error (CVE-2024-26766)
• kernel: RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem (CVE-2025-38022)
• kernel: Linux kernel: RDMA/rxe use-after-free vulnerability leading to potential arbitrary code execution (CVE-2025-38024)
• kernel: Linux kernel: Memory corruption in Squashfs due to incorrect block size calculation (CVE-2025-38415)
• kernel: Linux kernel: Denial of Service in ATM CLIP module via infinite recursion (CVE-2025-38459)
• kernel: Linux kernel: Denial of Service via out-of-bounds read in USB configuration parsing (CVE-2025-39760)
• kernel: mptcp: fix race condition in mptcp_schedule_work() (CVE-2025-40258)
• kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. (CVE-2025-40271)
• kernel: Linux kernel: Information disclosure and denial of service via out-of-bounds read in font glyph handling (CVE-2025-40322)
• kernel: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() (CVE-2022-50865)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: Linux kernel: irqchip/gic-v2m use-after-free vulnerability (CVE-2025-37819)
• kernel: RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem (CVE-2025-38022)
• kernel: Linux kernel use-after-free in eventpoll (CVE-2025-38349)
• kernel: io_uring/msg_ring: ensure io_kiocb freeing is deferred for RCU (CVE-2025-38453)
• kernel: net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (CVE-2025-38568)
• kernel: drm/xe: Fix vm_bind_ioctl double free bug (CVE-2025-38731)
• kernel: ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (CVE-2025-40154)
• kernel: net: use dst_dev_rcu() in sk_setup_caps() (CVE-2025-40170)
• kernel: ipv6: use RCU in ip6_xmit() (CVE-2025-40135)
• kernel: ipv6: use RCU in ip6_output() (CVE-2025-40158)
• kernel: Linux kernel: vsock vulnerability may lead to memory corruption (CVE-2025-40248)
• kernel: mptcp: fix race condition in mptcp_schedule_work() (CVE-2025-40258)
• kernel: devlink: rate: Unset parent pointer in devl_rate_nodes_destroy (CVE-2025-40251)
• kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. (CVE-2025-40271)
• kernel: Linux kernel: Out-of-bounds write in Bluetooth MGMT can lead to information disclosure and denial of service (CVE-2025-40294)
• kernel: Linux kernel: Information disclosure and denial of service in Bluetooth HCI event handling (CVE-2025-40301)
• kernel: Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once (CVE-2025-40318)
• kernel: net: atlantic: fix fragment overflow handling in RX path (CVE-2025-68301)
• kernel: Bluetooth: hci_sock: Prevent race in socket write iter and sock bind (CVE-2025-68305)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: net: openvswitch: fix nested key length validation in the set() action (CVE-2025-37789)
• kernel: Linux kernel: irqchip/gic-v2m use-after-free vulnerability (CVE-2025-37819)
• kernel: RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem (CVE-2025-38022)
• kernel: Linux kernel: RDMA/rxe use-after-free vulnerability leading to potential arbitrary code execution (CVE-2025-38024)
• kernel: Linux kernel: Memory corruption in Squashfs due to incorrect block size calculation (CVE-2025-38415)
• kernel: vsock/vmci: Clear the vmci transport packet properly when initializing it (CVE-2025-38403)
• kernel: Linux kernel: Denial of Service in ATM CLIP module via infinite recursion (CVE-2025-38459)
• kernel: Linux kernel: Data corruption and system instability due to improper io_uring/net buffer handling (CVE-2025-38730)
• kernel: Linux kernel: Denial of Service via out-of-bounds read in USB configuration parsing (CVE-2025-39760)
• kernel: net: use dst_dev_rcu() in sk_setup_caps() (CVE-2025-40170)
• kernel: ipv6: use RCU in ip6_xmit() (CVE-2025-40135)
• kernel: Bluetooth: ISO: Fix possible UAF on iso_conn_free (CVE-2025-40141)
• kernel: ipv6: use RCU in ip6_output() (CVE-2025-40158)
• kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. (CVE-2025-40271)
• kernel: Linux kernel ALSA USB audio driver: Buffer overflow leading to information disclosure and denial of service (CVE-2025-40269)
• kernel: Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once (CVE-2025-40318)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

• fs/proc: fix uaf in proc_readdir_de() {CVE-2025-40271}
• fs: fix UAF/GPF bug in nilfs_mdt_destroy {CVE-2022-2978}
• Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp {CVE-2023-53297}
• net: sched: sfb: fix null pointer access issue when sfb_init() fails {CVE-2022-50356}
• ALSA: usb-audio: Fix size validation in convert_chmap_v3()
• nfsd: don't ignore the return code of svc_proc_register() {CVE-2025-22026}
• net: usb: smsc75xx: Move packet length check to prevent kernel panic in skb_pull {CVE-2023-53104}
• net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class
• HID: stop exporting hid_snto32()
• HID: simplify snto32()
• HID: core: fix shift-out-of-bounds in hid_report_raw_event {CVE-2022-48978}
• HID: core: detect and skip invalid inputs to snto32()
• HID: core: don't use negative operands when shift

• fs/proc: fix uaf in proc_readdir_de() {CVE-2025-40271}
• fs: fix UAF/GPF bug in nilfs_mdt_destroy {CVE-2022-2978}
• Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp {CVE-2023-53297}
• net: sched: sfb: fix null pointer access issue when sfb_init() fails {CVE-2022-50356}
• ALSA: usb-audio: Fix size validation in convert_chmap_v3()
• nfsd: don't ignore the return code of svc_proc_register() {CVE-2025-22026}
• net: usb: smsc75xx: Move packet length check to prevent kernel panic in skb_pull {CVE-2023-53104}
• net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class
• HID: stop exporting hid_snto32()
• HID: simplify snto32()
• HID: core: fix shift-out-of-bounds in hid_report_raw_event {CVE-2022-48978}
• HID: core: detect and skip invalid inputs to snto32()
• HID: core: don't use negative operands when shift

• fs/proc: fix uaf in proc_readdir_de() {CVE-2025-40271}
• fs: fix UAF/GPF bug in nilfs_mdt_destroy {CVE-2022-2978}
• Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp {CVE-2023-53297}
• net: sched: sfb: fix null pointer access issue when sfb_init() fails {CVE-2022-50356}
• ALSA: usb-audio: Fix size validation in convert_chmap_v3()
• nfsd: don't ignore the return code of svc_proc_register() {CVE-2025-22026}
• net: usb: smsc75xx: Move packet length check to prevent kernel panic in skb_pull {CVE-2023-53104}
• net/sched: sch_qfq: Avoid triggering might_sleep in atomic context in qfq_delete_class
• HID: stop exporting hid_snto32()
• HID: simplify snto32()
• HID: core: fix shift-out-of-bounds in hid_report_raw_event {CVE-2022-48978}
• HID: core: detect and skip invalid inputs to snto32()
• HID: core: don't use negative operands when shift

• crypto: af_alg - Fix incorrect boolean values in af_alg_ctx {CVE-2025-40022}
• arm64: pensando: Must boot Ortano kernel with spin-table
• net/sched: adjust device watchdog timer to detect stopped queue at right time
• net/mlx5: Mark the mellanox graceful_period fix as out-of-tree change
• infiniband/xsigo: Replace BUG_ON with WARN_ON_ONCE.
• infiniband/xsigo: xsvnic_main: Remove unused functions
• infiniband/xsigo: xve_cm: Fix mixed code warning
• infiniband/xsigo: xve_ethtool: Remove unused variable 'priv'
• infiniband/xsigo: xve_ib: Fix misleading indentation
• infiniband/xsigo: xve_ib: Fix mixed code warning
• infiniband/xsigo: xve_verbs: Remove unused label 'out_free_pd'
• infiniband/xsigo: xve_main: Remove unused function 'xve_napi_del'
• infiniband/xsigo: xve_main: Fix mixed code warning
• infiniband/xsigo: xve_main: Fix misleading indentation
• inifinibad/xsigo: xsvnic_main: Remove unused variable 'xsvnic_ethtool_ops'
• infiniband/xsigo: xscore_impl: Remove unused label 'err_pd'
• rds: Fix jiffies type in struct rds_conn_path
• kernel: sysctl: Remove unused variable 'zero'
• crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg {CVE-2025-39964}
• RDMA/cm: Base cm_id destruction timeout on CMA values
• x86/its: Build fails with CONFIG_MITIGATION_ITS=n
• LTS tag: v5.4.302
• Input: pegasus-notetaker - fix potential out-of-bounds access {CVE-2025-68217}
• Input: remove third argument of usb_maxpacket()
• usb: deprecate the third argument of usb_maxpacket()
• fs/proc: fix uaf in proc_readdir_de() {CVE-2025-40271}
• pmdomain: imx: Fix reference count leak in imx_gpc_remove
• pmdomain: arm: scmi: Fix genpd leak on provider registration failure {CVE-2025-68204}
• net: netpoll: fix incorrect refcount handling causing incorrect cleanup {CVE-2025-68245}
• net: qede: Initialize qede_ll_ops with designated initializer
• net: ethernet: ti: netcp: Standardize knav_dma_open_channel to return NULL on error {CVE-2025-68220}
• ALSA: usb-audio: fix uac2 clock source at terminal parser
• mm/page_alloc: fix hash table order logging in alloc_large_system_hash()
• kconfig/nconf: Initialize the default locale at startup
• kconfig/mconf: Initialize the default locale at startup
• vsock: Ignore signal/timeout on connect() if already established {CVE-2025-40248}
• s390/ctcm: Fix double-kfree {CVE-2025-40253}
• net: openvswitch: remove never-working support for setting nsh fields {CVE-2025-40254}
• mlxsw: spectrum: Fix memory leak in mlxsw_sp_flower_stats()
• MIPS: Malta: Fix !EVA SOC-it PCI MMIO
• scsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show() {CVE-2025-68229}
• scsi: sg: Do not sleep in atomic context {CVE-2025-40259}
• Input: cros_ec_keyb - fix an invalid memory access {CVE-2025-40263}
• be2net: pass wrb_params in case of OS2BMC {CVE-2025-40264}
• isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe() {CVE-2025-68734}
• EDAC/altera: Use INTTEST register for Ethernet and USB SBE injection
• EDAC/altera: Handle OCRAM ECC enable after warm reset
• spi: Try to get ACPI GPIO IRQ earlier
• ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe {CVE-2025-68241}
• strparser: Fix signed/unsigned mismatch bug
• gcov: add support for GCC 15
• mm/ksm: fix flag-dropping behavior in ksm_madvise {CVE-2025-40040}
• ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd {CVE-2025-40275}
• drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE {CVE-2025-40277}
• ASoC: cs4271: Fix regulator leak on probe failure
• regulator: fixed: fix GPIO descriptor leak on register failure
• regulator: fixed: use dev_err_probe for register
• Bluetooth: L2CAP: export l2cap_chan_hold for modules
• net_sched: limit try_bulk_dequeue_skb() batches
• net_sched: remove need_resched() from qdisc_run()
• net/mlx5e: Fix wraparound in rate limiting for values above 255 Gbps
• net/mlx5e: Fix maxrate wraparound in threshold between units
• net: sched: act_ife: initialize struct tc_ife to fix KMSAN…

• HID: core: ensure the allocated report buffer can contain the reserved report ID {CVE-2025-38495}
• fs/proc: fix uaf in proc_readdir_de() {CVE-2025-40271}
• ALSA: usb-audio: Fix potential overflow of PCM transfer buffer {CVE-2025-40269}
• Bluetooth: ISO: Fix possible UAF on iso_conn_free {CVE-2025-40141}
• Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once {CVE-2025-40318}
• smb3: fix for slab out of bounds on mount to ksmbd {CVE-2025-38728}
• pptp: ensure minimal skb length in pptp_xmit() {CVE-2025-38574}
• ipv6: reject malicious packets in ipv6_gso_segment() {CVE-2025-38572}
• fbdev: fix potential buffer overflow in do_register_framebuffer() {CVE-2025-38702}
• i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path {CVE-2025-39911}
• bus: mhi: host: Detect events pointing to unexpected TREs {CVE-2025-39790}
• nvmet: fix out-of-bounds access in nvmet_enable_port {CVE-2025-37825}
• drm/xe: Make dma-fences compliant with the safe access rules {CVE-2025-38703}
• libceph: fix invalid accesses to ceph_connection_v1_info {CVE-2025-39880}
• fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass {CVE-2025-38396}
• anon_inode: explicitly block ->setattr()
• anon_inode: use a proper mode internally
• dynamic_dname(): drop unused dentry argument
• anon_inode: raise SB_I_NODEV and SB_I_NOEXEC
• Bluetooth: MGMT: Fix UAF on mgmt_remove_adv_monitor_complete {CVE-2025-38118}
• Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync {CVE-2024-58013}
• drm/xe: Fix vm_bind_ioctl double free bug {CVE-2025-38731}
• media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() {CVE-2025-38680}
• HID: core: ensure __hid_request reserves the report ID as the first byte
• wifi: mwifiex: Initialize the chan_stats array to zero {CVE-2025-39891}
• i40e: Fix potential invalid access when MAC list is empty {CVE-2025-39853}
• usb: core: config: Prevent OOB read in SS endpoint companion parsing {CVE-2025-39760}
• fs/buffer: fix use-after-free when call bh_read() helper {CVE-2025-39691}
• drm/i915: Protect access to driver and timeline name
• sync_file: Protect access to driver and timeline name
• dma-fence: Add safe access helpers and document the rules
• VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify {CVE-2025-38102}
• net: phylink: add lock for serializing concurrent pl->phydev writes with resolver {CVE-2025-39905}
• HID: multitouch: fix slab out-of-bounds access in mt_report_fixup() {CVE-2025-39806}
• vsock: Do not allow binding to VMADDR_PORT_ANY {CVE-2025-38618}
• mm/memory-failure: fix VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoison memory {CVE-2025-39883}
• md/raid1: Fix stack memory use after return in raid1_reshape {CVE-2025-38445}
• drm/i915/gt: Fix timeline left held on VMA alloc error {CVE-2025-38389}
• ALSA: usb-audio: Fix out-of-bounds read in snd_usb_get_audioformat_uac3() {CVE-2025-38249}
• i40e: remove read access to debugfs files {CVE-2025-39901}
• wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work {CVE-2025-39863}
• bnxt_en: Fix memory corruption when FW resources change during ifdown {CVE-2025-39810}
• atm: clip: Fix infinite recursive call of clip_push(). {CVE-2025-38459}
• nbd: fix uaf in nbd_genl_connect() error path {CVE-2025-38443}
• Squashfs: check return result of sb_min_blocksize {CVE-2025-38415}
• vsock/vmci: Clear the vmci transport packet properly when initializing it {CVE-2025-38403}
• regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods {CVE-2025-38395}
• virtio-net: ensure the received length does not exceed allocated size {CVE-2025-38375}
• ftrace: Fix UAF when lookup kallsym after ftrace disabled {CVE-2025-38346}
• sctp: avoid NULL dereference when chunk data buffer is missing {CVE-2025-40240}
• net: atm: fix /proc/net/atm/lec handling {CVE-2025-38180}
• software node: Correct a OOB check in software_node_get_reference_args() {CVE-2025-38342}
• net: atm: add lec_mutex {CVE-2025-38323} -…

• net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit {CVE-2025-39766}
• NFSD: Avoid calling OPDESC() with ops->opnum == OP_ILLEGAL {CVE-2023-53680}
• scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() {CVE-2023-53676}
• KVM: x86: use array_index_nospec with indices that come from guest {CVE-2025-39823}
• ftrace: Also allocate and copy hash for reading of filter files {CVE-2025-39689}
• ext4: improve error handling from ext4_dirhash() {CVE-2023-53473}
• rcu: Protect ->defer_qs_iw_pending from data race {CVE-2025-39749}
• ring-buffer: Fix deadloop issue on reading trace_pipe {CVE-2023-53668}
• fs/proc: fix uaf in proc_readdir_de() {CVE-2025-40271}
• ALSA: usb-audio: Fix potential overflow of PCM transfer buffer {CVE-2025-40269}
• Bluetooth: ISO: Fix possible UAF on iso_conn_free {CVE-2025-40141}
• pptp: ensure minimal skb length in pptp_xmit() {CVE-2025-38574}
• lib: cpu_rmap: Avoid use after free on rmap->obj array entries {CVE-2023-53484}
• ipv6: reject malicious packets in ipv6_gso_segment() {CVE-2025-38572}
• fbdev: Fix vmalloc out-of-bounds write in fast_imageblit {CVE-2025-38685}
• fbdev: fix potential buffer overflow in do_register_framebuffer() {CVE-2025-38702}
• i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path {CVE-2025-39911}
• libceph: fix invalid accesses to ceph_connection_v1_info {CVE-2025-39880}
• bus: mhi: host: Detect events pointing to unexpected TREs {CVE-2025-39790}
• nvmet: fix out-of-bounds access in nvmet_enable_port {CVE-2025-37825}
• net: core: remove unnecessary frame_sz check in bpf_xdp_adjust_tail() {CVE-2023-54155}
• wifi: mwifiex: Initialize the chan_stats array to zero {CVE-2025-39891}
• i40e: Fix potential invalid access when MAC list is empty {CVE-2025-39853}
• media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() {CVE-2025-38680}
• fs/buffer: fix use-after-free when call bh_read() helper {CVE-2025-39691}
• net/mlx5: Devcom, fix error flow in mlx5_devcom_register_device {CVE-2023-54015}
• x86/sev: Make enc_dec_hypercall() accept a size instead of npages {CVE-2023-53996}
• page_pool: Fix use-after-free in page_pool_recycle_in_ring {CVE-2025-38129}
• page_pool: fix inconsistency for page_pool_ring_[un]lock()
• net: page_pool: use in_softirq() instead {CVE-2025-38129}
• vsock: Ignore signal/timeout on connect() if already established {CVE-2025-40248}
• vsock: avoid to close connected socket after the timeout {CVE-2025-40248}
• sctp: avoid NULL dereference when chunk data buffer is missing {CVE-2025-40240}
• smb: client: let recv_done verify data_offset, data_length and remaining_data_length {CVE-2025-39933}
• net: phylink: add lock for serializing concurrent pl->phydev writes with resolver {CVE-2025-39905}
• i40e: validate ring_len parameter against hardware-specific values
• i40e: add validation for ring_len param {CVE-2025-39973}
• i40e: increase max descriptors for XL710
• i40e: remove read access to debugfs files {CVE-2025-39901}
• mm/memory-failure: fix VM_BUG_ON_PAGE(PagePoisoned(page)) when unpoison memory {CVE-2025-39883}
• wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work {CVE-2025-39863}
• i2c: tegra: check msg length in SMBUS block read {CVE-2025-38425}
• regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods {CVE-2025-38395}
• virtio-net: ensure the received length does not exceed allocated size {CVE-2025-38375}
• VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify {CVE-2025-38102}
• vsock/vmci: Clear the vmci transport packet properly when initializing it {CVE-2025-38403}
• can: bcm: add locking for bcm_op runtime updates {CVE-2025-38004}
• scsi: lpfc: Prevent lpfc_debugfs_lockstat_write() buffer overflow {CVE-2023-54102}
• tcp: fix a signed-integer-overflow bug in tcp_add_backlog() {CVE-2022-50865}
• tcp: minor optimization in tcp_add_backlog() {CVE-2022-50865}
• block, bfq: fix uaf for bfqq in bic_set_bfqq() {CVE-2023-52983}
• block, bfq: replace 0/1 with…

• wifi: iwlwifi: mvm: guard against invalid STA ID on removal {CVE-2024-36921}
• ASoC: topology: Fix references to freed memory {CVE-2024-41069}
• net/sched: act_mirred: don't override retval if we already lost the skb {CVE-2024-26739}
• drivers: base: Free devm resources when unregistering a device {CVE-2023-53596}
• usb: core: config: Prevent OOB read in SS endpoint companion parsing {CVE-2025-39760}
• fbdev: Fix vmalloc out-of-bounds write in fast_imageblit {CVE-2025-38685}
• net/mlx5e: Avoid field-overflowing memcpy() {CVE-2022-48744}
• ext4: fix use-after-free in ext4_orphan_cleanup {CVE-2022-50673}
• xfrm: fix slab-use-after-free in decode_session6 {CVE-2023-53500}
• net: bridge: xmit: make sure we have at least eth header len bytes {CVE-2024-38538}
• NFSD: Avoid calling OPDESC() with ops->opnum == OP_ILLEGAL {CVE-2023-53680}
• perf/core: Exit early on perf_mmap() fail {CVE-2025-38565}
• i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path {CVE-2025-39911}
• fs/proc: fix uaf in proc_readdir_de() {CVE-2025-40271}
• virtio_net: fix xdp_rxq_info bug after suspend/resume {CVE-2022-49687}
• NFSD: Fix the behavior of READ near OFFSET_MAX {CVE-2022-48827}
• usb: xhci: Apply the link chain quirk on NEC isoc endpoints {CVE-2025-22022}
• Bluetooth: RFCOMM: Fix not validating setsockopt user input {CVE-2024-35966}
• Bluetooth: L2CAP: Fix not validating setsockopt user input {CVE-2024-35965}
• Bluetooth: SCO: Fix not validating setsockopt user input {CVE-2024-35967}
• netfilter: nf_tables: prefer nft_chain_validate {CVE-2024-41042}
• netfilter: validate user input for expected length {CVE-2024-35896}
• erspan: do not use skb_mac_header() in ndo_start_xmit() {CVE-2023-53053}
• scsi: libsas: Fix use-after-free bug in smp_execute_task_sg() {CVE-2022-50422}
• i40e: remove read access to debugfs files {CVE-2025-39901}
• wifi: cfg80211: check A-MSDU format more carefully {CVE-2024-35937}
• Bluetooth: hci_sock: Prevent race in socket write iter and sock bind {CVE-2025-68305}
• RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem {CVE-2025-38022}
• netfilter: allow exp not to be removed in nf_ct_find_expectation {CVE-2023-52927}
• dm-bufio: don't schedule in atomic context {CVE-2025-37928}
• HID: multitouch: Add NULL check in mt_input_configured {CVE-2024-58020}
• netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX {CVE-2025-38201}
• fs: writeback: fix use-after-free in __mark_inode_dirty() {CVE-2025-39866}
• tracing/histograms: Add histograms to hist_vars if they have referenced variables {CVE-2023-53560}
• netfilter: conntrack: Avoid nf_ct_helper_hash uses after free {CVE-2023-53619}
• drm/dp_mst: Fix MST sideband message body length check {CVE-2024-56616}
• KVM: SVM: Flush pages under kvm->lock to fix UAF in svm_register_enc_region() {CVE-2024-35791}
• scsi: ses: Fix slab-out-of-bounds in ses_intf_remove() {CVE-2023-53521}
• dm cache: Fix UAF in destroy() {CVE-2022-50496}
• xhci: Remove device endpoints from bandwidth list when freeing the device {CVE-2022-50470}
• Bluetooth: L2CAP: Fix user-after-free {CVE-2022-50386}
• mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats {CVE-2025-68800}
• net/sched: Enforce that teql can only be used as root qdisc {CVE-2026-23074}
• igb: Do not bring the device up after non-fatal error {CVE-2024-50040}
• wifi: mwifiex: Initialize the chan_stats array to zero {CVE-2025-39891}
• HID: asus: fix UAF via HID_CLAIMED_INPUT validation {CVE-2025-39824}
• fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds {CVE-2025-40304}
• HID: multitouch: Correct devm device reference for hidinput input_dev name {CVE-2023-53454}
• udf: Do not bother merging very long extents {CVE-2023-53506}
• wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() {CVE-2022-50551}
• ring-buffer: Sync IRQ works before buffer destruction {CVE-2023-53587}
• dm integrity: call kmem_cache_destroy() in dm_integrity_init() error path…

• crypto: algif_aead - Fix minimum RX size check for decryption
• crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl
• crypto: authencesn - Fix src offset when decrypting in-place
• crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption
• crypto: authenc - use memcpy_sglist() instead of null skcipher
• crypto: algif_aead - snapshot IV for async AEAD requests
• crypto: algif_aead - Revert to operating out-of-place
• crypto: algif_aead - use memcpy_sglist() instead of null skcipher
• crypto: scatterwalk - Backport memcpy_sglist()
• crypto: authencesn - reject too-short AAD (assoclen<8) to match ESP/ESN spec
• nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec {CVE-2026-22998}
• xfrm: add NULL check in xfrm_update_ae_params {CVE-2023-3772}
• sctp: check send stream number after wait_for_sndbuf {CVE-2023-53296}
• ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value {CVE-2022-50327}
• ext4: fix uninititialized value in 'ext4_evict_inode' {CVE-2022-50546}
• tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock(). {CVE-2025-40149}
• bpf, cpumap: Make sure kthread is running before map update returns {CVE-2023-53577}
• net: add dst_dev_rcu() helper for safe dst->dev access {CVE-2025-40135}
• net/sched: cls_u32: use skb_header_pointer_careful() {CVE-2026-23204}
• net: add skb_header_pointer_careful() helper
• net/sched: sch_hfsc: upgrade 'rt' to 'sc' when it becomes a inner curve {CVE-2023-4623}
• ip_vti: fix potential slab-use-after-free in decode_session6 {CVE-2023-53559}
• e1000e: fix heap overflow in e1000_set_eeprom {CVE-2025-39898}
• ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control {CVE-2025-39751}
• md/raid10: fix null-ptr-deref of mreplace in raid10_sync_request {CVE-2023-53380}
• HID: uclogic: Correct devm device reference for hidinput input_dev name {CVE-2023-54207}
• ASoC: da7219: Fix an error handling path in da7219_register_dai_clks() {CVE-2022-50698}
• selinux: enable use of both GFP_KERNEL and GFP_ATOMIC in convert_context() {CVE-2022-50699}
• scsi: qla2xxx: Check valid rport returned by fc_bsg_to_rport() {CVE-2023-54014}
• ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() {CVE-2025-71085}
• ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() {CVE-2026-23089}
• scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() {CVE-2026-23193}
• drm/i915/gvt: fix gvt debugfs destroy {CVE-2023-54098}
• nfsd: provide locking for v4_end_grace {CVE-2026-22980}
• dm flakey: don't corrupt the zero page {CVE-2023-54317}
• drm/amdkfd: Fix double release compute pasid {CVE-2022-50303}
• RDMA/srpt: Fix a use-after-free {CVE-2022-50129}
• RDMA/srpt: Introduce a reference count in struct srpt_device
• RDMA/srpt: Duplicate port name members
• KVM: x86: Reset IRTE to host control if new route isn't postable {CVE-2025-37885}
• ipvlan: add ipvlan_route_v6_outbound() helper {CVE-2023-52796}
• mmc: core: use scnprintf() instead of sprintf() in sysfs show functions {CVE-2022-49267}
• rcu: Fix rcu_read_unlock() deadloop due to IRQ work {CVE-2025-39744}
• net/mlx5: Add a timeout to acquire the command queue semaphore {CVE-2024-38556}
• virtio-net: ensure the received length does not exceed allocated size {CVE-2025-38375}
• cacheinfo: Fix shared_cpu_map to handle shared caches at different levels {CVE-2023-53254}
• RDMA/mlx5: Return the firmware result upon destroying QP/RQ {CVE-2023-53286}
• RDMA/rxe: Fix mr->map double free {CVE-2022-50543}
• wifi: ath9k: Fix use-after-free in ath9k_hif_usb_disconnect() {CVE-2022-50881}
• tcp: fix a signed-integer-overflow bug in tcp_add_backlog() {CVE-2022-50865}
• NFSD: Protect against send buffer overflow in NFSv2 READ {CVE-2022-43945}
• perf/aux: Fix AUX buffer serialization {CVE-2024-46713}
• usb: xhci: Fix isochronous Ring Underrun/Overrun event handling {CVE-2025-37882}
• usb: xhci: Complete 'error mid TD' transfers when handling Missed Service
• usb: xhci: remove…

• CVE-2026-72463
  • xfrm: Fix dev use-after-free in xfrm async resumption {CVE-2026-72463}
• CVE-2026-64600
  • xfs: resample the data fork mapping after cycling ILOCK {CVE-2026-64600}
• CVE-2026-46175
  • f2fs: fix fsck inconsistency caused by FGGC of node block {CVE-2026-46175}
• CVE-2025-68254
  • staging: rtl8723bs: fix out-of-bounds read in OnBeacon ESR IE parsing {CVE-2025-68254}
• CVE-2025-68255
  • staging: rtl8723bs: fix stack buffer overflow in OnAssocReq IE parsing {CVE-2025-68255}
• CVE-2026-64268
  • RDMA/siw: bound Read Response placement to the RREAD length {CVE-2026-64268}
• CVE-2025-68286
  • drm/amd/display: Check NULL before accessing {CVE-2025-68286}
• CVE-2026-53024
  • greybus: raw: fix use-after-free if write is called after disconnect {CVE-2026-53024}
• CVE-2026-53025
  • greybus: raw: fix use-after-free on cdev close {CVE-2026-53025}
• CVE-2026-52934
  • batman-adv: tvlv: reject oversized TVLV packets {CVE-2026-52934}
• CVE-2025-68303
  • platform/x86: intel: punit_ipc: fix memory corruption {CVE-2025-68303}
• CVE-2026-64280
  • fpga: dfl-afu: validate DMA mapping length in afu_dma_map_region() {CVE-2026-64280}
• CVE-2026-64188
  • net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() {CVE-2026-64188}
• CVE-2026-64109
  • af_unix: Fix UAF read of tail->len in unix_stream_data_wait() {CVE-2026-64109}
• CVE-2026-64274
  • Input: goodix - clamp the device-reported contact count {CVE-2026-64274}
• CVE-2026-64270
  • Input: mms114 - reject an oversized device packet size {CVE-2026-64270}
• CVE-2026-64093
  • batman-adv: tp_meter: directly shut down timer on cleanup {CVE-2026-64093}
• CVE-2026-64091
  • batman-adv: tt: fix TOCTOU race for reported vlans {CVE-2026-64091}
• CVE-2026-53329
  • drm/amd/display: Use krealloc_array() in dal_vector_reserve() {CVE-2026-53329}
• CVE-2026-64298
  • NFSv4: include MAY_WRITE in open permission mask for O_TRUNC {CVE-2026-64298}
• CVE-2026-64276
  • Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count {CVE-2026-64276}
• CVE-2026-64273
  • Input: iforce - bound the device-reported force-feedback effect index {CVE-2026-64273}
• CVE-2026-64271
  • Input: touchwin - reset the packet index on every complete packet {CVE-2026-64271}
• CVE-2026-64266
  • fuse: re-lock request before returning from fuse_ref_folio() {CVE-2026-64266}
• CVE-2026-64191
  • i2c: stub: Reject I2C block transfers with invalid length {CVE-2026-64191}
• CVE-2026-64189
  • netfilter: ipset: fix race between dump and ip_set_list resize {CVE-2026-64189}
• CVE-2026-31786
  • Buffer overflow in drivers/xen/sys-hypervisor.c {CVE-2026-31786}
• CVE-2025-68799
  • caif: fix integer underflow in cffrml_receive() {CVE-2025-68799}
• CVE-2025-68302
  • net: sxgbe: fix potential NULL dereference in sxgbe_rx() {CVE-2025-68302}
• CVE-2025-40243
  • hfs: fix KMSAN uninit-value issue in hfs_find_set_zero_bits() {CVE-2025-40243}
• CVE-2025-40233
  • ocfs2: clear extent cache after moving/defragmenting extents {CVE-2025-40233}
• CVE-2026-23269
  • apparmor: validate DFA start states are in bounds in unpack_pdb {CVE-2026-23269}
• CVE-2026-43249
  • 9p/xen: protect xen_9pfs_front_free against concurrent calls {CVE-2026-43249}
• CVE-2026-31657
  • batman-adv: hold claim backbone gateways by reference {CVE-2026-31657}
• CVE-2026-31598
  • ocfs2: fix possible deadlock between unlink and dio_end_io_write {CVE-2026-31598}
• CVE-2026-31768
  • iio: adc: ti-adc161s626: use DMA-safe memory for spi_read() {CVE-2026-31768}
• CVE-2026-23216
  • scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() {CVE-2026-23216} *…

• CVE-2022-49416
  • wifi: mac80211: fix use-after-free in chanctx code {CVE-2022-49416}
• CVE-2022-49685
  • iio: trigger: sysfs: fix use-after-free on remove {CVE-2022-49685}
• CVE-2021-47670
  • can: peak_usb: fix use after free bugs {CVE-2021-47670}
• CVE-2026-98706
  • wifi: mac80211: drain PS delivery work during station teardown {CVE-2026-98706}
• CVE-2026-98610
  • net/sched: sch_hfsc: bound the classify inner-filter walk with a drift budget {CVE-2026-98610}
• CVE-2026-98548
  • sctp: discard the rest of the packet on a stale-cookie error {CVE-2026-98548}
• CVE-2026-98614
  • sctp: avoid livelock while updating retransmit path {CVE-2026-98614}
• CVE-2026-98547
  • af_packet: fix integer overflow in prb_calc_retire_blk_tmo() {CVE-2026-98547}
• CVE-2026-98579
  • nfc: llcp: fix sdreq TLV list leak on parse/alloc/send failure {CVE-2026-98579}
• CVE-2026-98581
  • nfc: llcp: Fix list corruption / refcount desync in nfc_llcp_recv_dm() {CVE-2026-98581}
• CVE-2026-98577
  • nfc: llcp: fix WKS SAP hijacking via prefix match in nfc_llcp_wks_sap() {CVE-2026-98577}
• CVE-2026-98482
  • nfc: llcp: drop truncated I/RR/RNR PDUs in nfc_llcp_recv_hdlc() {CVE-2026-98482}
• CVE-2026-98576
  • nfc: llcp: fix slab-out-of-bounds reads when logging service names {CVE-2026-98576}
• CVE-2026-98624
  • netfilter: nfnetlink_queue: hold nfnl mutex in event notifier {CVE-2026-98624}
  • netlink: use blocking notifier {CVE-2026-98624}
• CVE-2026-98794
  • ipvs: filter some flags received in the backup server {CVE-2026-98794}
• CVE-2026-98829
  • wifi: mac80211: drop oversized fragments to avoid extra_len overflow {CVE-2026-98829}
• CVE-2026-98708
  • wifi: mac80211: keep paired old chanctx alive {CVE-2026-98708}
• CVE-2026-98707
  • wifi: mac80211: shut down RX BA session timer on teardown {CVE-2026-98707}
• CVE-2026-98532
  • ipv6: do not let ipv6_find_hdr() return an offset past the packet end {CVE-2026-98532}
• CVE-2026-98541
  • fou: reject omitted FOU_ATTR_IPPROTO on FOU_ENCAP_DIRECT {CVE-2026-98541}
• CVE-2026-98461
  • Bluetooth: hci_sock: validate event length before filtering {CVE-2026-98461}
• CVE-2026-98621
  • net: gue: reject invalid REMCSUM offsets {CVE-2026-98621}
• CVE-2026-98526
  • llc: reserve device headroom for allocated frames {CVE-2026-98526}
• CVE-2026-98555
  • llc: fix skb UAF and leaks on llc_mac_hdr_init() failure {CVE-2026-98555}
• CVE-2026-98573
  • net: skbuff: fix pull-bound underflow in skb_checksum_setup_ipv6() {CVE-2026-98573}
• CVE-2026-98739
  • Bluetooth: RFCOMM: Fix initial port reference race {CVE-2026-98739}
• CVE-2026-98457
  • Bluetooth: L2CAP: validate frame length before control and FCS access {CVE-2026-98457}
• CVE-2026-98460
  • Bluetooth: hci_sock: reject out-of-range OCF values {CVE-2026-98460}
• CVE-2026-98856
  • kprobes: Skip disarmed probes when checking optkprobe overlap {CVE-2026-98856}
• CVE-2026-98636
  • squashfs: Add dictionary size range check to prevent shift-out-of-bounds {CVE-2026-98636}
• CVE-2026-98681
  • smb: client: split cifsFileInfo bitfields to avoid shared-byte RMW races {CVE-2026-98681}
• CVE-2026-98771
  • usb: storage: sierra_ms: reject short SWoC info transfers {CVE-2026-98771}
• CVE-2026-98772
  • USB: serial: fix port tear down use-after-free {CVE-2026-98772}
• CVE-2026-98696
  • USB: serial: fix driver deregistration order {CVE-2026-98696}
• CVE-2026-98697
  • USB: serial: fix dynamic id driver deregistration race {CVE-2026-98697}
• CVE-2026-98769
  • usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd {CVE-2026-98769}
• CVE-2026-98764
  • usb: gadget: f_fs: Fix NULL pointer dereference in …

Upstream kernel version 6.6.120 fixes bugs and vulnerabilities. The kmod-virtualbox & kmod-xtables-addons packages have been updated to work with this new kernel.

Vanilla upstream kernel version 6.6.120 fixes bugs and vulnerabilities. For information about the vulnerabilities see the links.

The SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues

The following security issues were fixed:

• CVE-2025-38704: rcu/nocb: Fix possible invalid rdp's->nocb_cb_kthread pointer (bsc#1254408).
• CVE-2025-39880: ceph: fix race condition validating r_parent before applying state (bsc#1250388).
• CVE-2025-39977: futex: Prevent use-after-free during requeue-PI (bsc#1252046).
• CVE-2025-40042: tracing: Fix race condition in kprobe initialization causing NULL pointer dereference (bsc#1252861).
• CVE-2025-40123: bpf: Enforce expected_attach_type for tailcall compatibility (bsc#1253365).
• CVE-2025-40130: scsi: ufs: core: Fix data race in CPU latency PM QoS request handling
• CVE-2025-40160: xen/events: Cleanup find_virq() return codes (bsc#1253400).
• CVE-2025-40167: ext4: detect invalid INLINE_DATA + EXTENTS flag combination (bsc#1253458).
• CVE-2025-40170: net: use dst_dev_rcu() in sk_setup_caps() (bsc#1253413).
• CVE-2025-40179: ext4: verify orphan file size is not too big (bsc#1253442).
• CVE-2025-40190: ext4: guard against EA inode refcount underflow in xattr update (bsc#1253623).
• CVE-2025-40214: af_unix: Initialise scc_index in unix_add_edge() (bsc#1254961).
• CVE-2025-40215: xfrm: delete x->tunnel as we delete x (bsc#1254959).
• CVE-2025-40218: mm/damon/vaddr: do not repeat pte_offset_map_lock() until success (bsc#1254964).
• CVE-2025-40220: fuse: fix livelock in synchronous file put from fuseblk workers (bsc#1254520).
• CVE-2025-40231: vsock: fix lock inversion in vsock_assign_transport() (bsc#1254815).
• CVE-2025-40233: ocfs2: clear extent cache after moving/defragmenting extents (bsc#1254813).
• CVE-2025-40237: fs/notify: call exportfs_encode_fid with s_umount (bsc#1254809).
• CVE-2025-40238: net/mlx5: Fix IPsec cleanup over MPV device (bsc#1254871).
• CVE-2025-40239: net: phy: micrel: always set shared->phydev for LAN8814 (bsc#1254868).
• CVE-2025-40242: gfs2: Fix unlikely race in gdlm_put_lock (bsc#1255075).
• CVE-2025-40246: xfs: fix out of bounds memory read error in symlink repair (bsc#1254861).
• CVE-2025-40248: vsock: Ignore signal/timeout on connect() if already established (bsc#1254864).
• CVE-2025-40250: net/mlx5: Clean up only new IRQ glue on request_irq() failure (bsc#1254854).
• CVE-2025-40251: devlink: rate: Unset parent pointer in devl_rate_nodes_destroy (bsc#1254856).
• CVE-2025-40252: net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end() (bsc#1254849).
• CVE-2025-40254: net: openvswitch: remove never-working support for setting nsh fields (bsc#1254852).
• CVE-2025-40255: net: core: prevent NULL deref in generic_hwtstamp_ioctl_lower() (bsc#1255156).
• CVE-2025-40258: mptcp: fix race condition in mptcp_schedule_work() (bsc#1254843).
• CVE-2025-40264: be2net: pass wrb_params in case of OS2BMC (bsc#1254835).
• CVE-2025-40268: cifs: client: fix memory leak in smb3_fs_context_parse_param (bsc#1255082).
• CVE-2025-40271: fs/proc: fix uaf in proc_readdir_de() (bsc#1255297).
• CVE-2025-40274: KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying (bsc#1254830).
• CVE-2025-40276: drm/panthor: Flush shmem writes before mapping buffers CPU-uncached (bsc#1254824).
• CVE-2025-40278: net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak (bsc#1254825).
• CVE-2025-40279: net: sched: act_connmark: initialize struct tc_ife to fix kernel leak (bsc#1254846).
• CVE-2025-40280: tipc: Fix use-after-free in tipc_mon_reinit_self() (bsc#1254847).
• CVE-2025-40292: virtio-net: fix received length check in big packets (bsc#1255175).
• CVE-2025-40293: iommufd: Don't overflow during division for dirty tracking (bsc#1255179).
• CVE-2025-40297: net: bridge: fix use-after-free due to MST port state bypass (bsc#1255187).
• CVE-2025-40319: bpf: Sync pending IRQ work before freeing ring buffer (bsc#1254794).
• CVE-2025-40328: smb: client: fix potential UAF in smb2_close_cached_fid() (bsc#1254624).
• CVE-2025-40330: bnxt_en: Shutdown FW…

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