CVE-2025-38556

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 packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

• kernel: vsock: Fix transport_* TOCTOU (CVE-2025-38461)

• kernel: do_change_type(): refuse to operate on unmounted/not ours mounts (CVE-2025-38498)

• kernel: HID: core: Harden s32ton() against conversion to 0 bits (CVE-2025-38556)

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: HID: core: Harden s32ton() against conversion to 0 bits (CVE-2025-38556)

• kernel: eventpoll: Fix semi-unbounded recursion (CVE-2025-38614)

• kernel: ALSA: usb-audio: Validate UAC3 cluster segment descriptors (CVE-2025-39757)

• kernel: crypto: seqiv - Handle EBUSY correctly (CVE-2023-53373)

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: HID: core: Harden s32ton() against conversion to 0 bits (CVE-2025-38556)

• kernel: wifi: ath12k: Decrement TID on RX peer frag setup error handling (CVE-2025-39761)

• kernel: ALSA: usb-audio: Validate UAC3 cluster segment descriptors (CVE-2025-39757)

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.

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

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

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

Root has patched CVE-2025-38556 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available.

Root has patched CVE-2025-38556 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.

In the Linux kernel, the following vulnerability has been resolved: HID: core: Harden s32ton() against conversion to 0 bits Testing by the syzbot fuzzer showed that the HID core gets a shift-out-of-bounds exception when it tries to convert a 32-bit quantity to a 0-bit quantity. Ideally this should never occur, but there are buggy devices and some might have a report field with size set to zero; we shouldn't reject the report or the device just because of that. Instead, harden the s32ton() routine so that it returns a reasonable result instead of crashing when it is called with the number of bits set to 0 -- the same as what snto32() does.

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

Security Fix(es):

• kernel: vsock: Fix transport_* TOCTOU (CVE-2025-38461)
• kernel: do_change_type(): refuse to operate on unmounted/not ours mounts (CVE-2025-38498)
• kernel: HID: core: Harden s32ton() against conversion to 0 bits (CVE-2025-38556)

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: HID: core: Harden s32ton() against conversion to 0 bits (CVE-2025-38556)
• kernel: eventpoll: Fix semi-unbounded recursion (CVE-2025-38614)
• kernel: ALSA: usb-audio: Validate UAC3 cluster segment descriptors (CVE-2025-39757)
• kernel: crypto: seqiv - Handle EBUSY correctly (CVE-2023-53373)

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: HID: core: Harden s32ton() against conversion to 0 bits (CVE-2025-38556)
• kernel: wifi: ath12k: Decrement TID on RX peer frag setup error handling (CVE-2025-39761)
• kernel: ALSA: usb-audio: Validate UAC3 cluster segment descriptors (CVE-2025-39757)

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:

HID: core: Harden s32ton() against conversion to 0 bits

Testing by the syzbot fuzzer showed that the HID core gets a shift-out-of-bounds exception when it tries to convert a 32-bit quantity to a 0-bit quantity. Ideally this should never occur, but there are buggy devices and some might have a report field with size set to zero; we shouldn't reject the report or the device just because of that.

Instead, harden the s32ton() routine so that it returns a reasonable result instead of crashing when it is called with the number of bits set to 0 -- the same as what snto32() does.

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

HID: core: Harden s32ton() against conversion to 0 bits

Testing by the syzbot fuzzer showed that the HID core gets a shift-out-of-bounds exception when it tries to convert a 32-bit quantity to a 0-bit quantity. Ideally this should never occur, but there are buggy devices and some might have a report field with size set to zero; we shouldn't reject the report or the device just because of that.

Instead, harden the s32ton() routine so that it returns a reasonable result instead of crashing when it is called with the number of bits set to 0 -- the same as what snto32() does.

• x86/kvm: Disable kvmclock on all CPUs on shutdown {CVE-2021-47110}
• posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() {CVE-2025-38352}
• cifs: fix double free race when mount fails in cifs_get_root() {CVE-2022-48919}
• aio: mark AIO pseudo-fs noexec {CVE-2016-10044}
• cifs: potential buffer overflow in handling symlinks {CVE-2022-49058}
• NFSD: fix race between nfsd registration and exports_proc {CVE-2025-38232}
• nfsd: register pernet ops last, unregister first {CVE-2025-38232}
• do_change_type(): refuse to operate on unmounted/not ours mounts {CVE-2025-38498}
• net: atm: fix /proc/net/atm/lec handling {CVE-2025-38180}
• net: atm: add lec_mutex {CVE-2025-38180}
• SUNRPC: make sure cache entry active before cache_show {CVE-2024-53174}
• scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() {CVE-2025-38399}
• scsi: target: Fix crash during SPEC_I_PT handling {CVE-2025-38399}
• mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race {CVE-2025-38085}
• drivers:md:fix a potential use-after-free bug {CVE-2022-50022}
• ext4: avoid resizing to a partial cluster size {CVE-2022-50020}
• HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() {CVE-2025-21928}
• net/sched: Abort __tc_modify_qdisc if parent class does not exist {CVE-2025-38457}
• misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() {CVE-2022-49788}
• dlm: fix plock invalid read {CVE-2022-49407}
• net: usb: smsc75xx: Limit packet length to skb->len {CVE-2023-53125}
• scsi: libfc: Fix use after free in fc_exch_abts_resp() {CVE-2022-49114}
• crypto: algif_hash - fix double free in hash_accept {CVE-2025-38079}
• HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556}
• HID: core: ensure the allocated report buffer can contain the reserved report ID {CVE-2025-38495}
• ext4: Fix possible corruption when moving a directory {CVE-2023-53137}
• ceph: avoid putting the realm twice when decoding snaps fails {CVE-2022-49770}
• vsock/vmci: Clear the vmci transport packet properly when initializing it {CVE-2025-38403}
• HID: core: do not bypass hid_hw_raw_request {CVE-2025-38494}
• sch_hfsc: make hfsc_qlen_notify() idempotent {CVE-2025-38177}
• ext4: check dot and dotdot of dx_root before making dir indexed {CVE-2024-42305}
• ALSA: bcd2000: Fix a UAF bug on the error path of probing {CVE-2022-50229}
• dm ioctl: prevent potential spectre v1 gadget {CVE-2022-49122}
• net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too {CVE-2025-37823}
• md-raid10: fix KASAN warning {CVE-2022-50211}
• scsi: lpfc: Use memcpy() for BIOS version {CVE-2025-38332}
• ACPICA: Refuse to evaluate a method if arguments are missing {CVE-2025-38386}
• media: cxusb: no longer judge rbuf when the write fails {CVE-2025-38229}
• ipc: fix to protect IPCS lookups using RCU {CVE-2025-38212}
• ext4: fix off-by-one error in do_split {CVE-2025-23150}
• perf/core: Fix WARN_ON(!ctx) in __free_event() for partial init {CVE-2025-37878}
• sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() {CVE-2025-38000}
• i40e: fix MMIO write access to an invalid page in i40e_clear_hw {CVE-2025-38200}

• x86/kvm: Disable kvmclock on all CPUs on shutdown {CVE-2021-47110}
• posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() {CVE-2025-38352}
• cifs: fix double free race when mount fails in cifs_get_root() {CVE-2022-48919}
• aio: mark AIO pseudo-fs noexec {CVE-2016-10044}
• cifs: potential buffer overflow in handling symlinks {CVE-2022-49058}
• NFSD: fix race between nfsd registration and exports_proc {CVE-2025-38232}
• nfsd: register pernet ops last, unregister first {CVE-2025-38232}
• net: atm: fix use after free in lec_send() {CVE-2025-22004}
• net: atlantic: fix aq_vec index out of range error {CVE-2022-50066}
• do_change_type(): refuse to operate on unmounted/not ours mounts {CVE-2025-38498}
• net: atm: fix /proc/net/atm/lec handling {CVE-2025-38180}
• net: atm: add lec_mutex {CVE-2025-38180}
• SUNRPC: make sure cache entry active before cache_show {CVE-2024-53174}
• scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() {CVE-2025-38399}
• scsi: target: Fix crash during SPEC_I_PT handling {CVE-2025-38399}
• mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race {CVE-2025-38085}
• drivers:md:fix a potential use-after-free bug {CVE-2022-50022}
• ext4: avoid resizing to a partial cluster size {CVE-2022-50020}
• HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() {CVE-2025-21928}
• net/sched: Abort __tc_modify_qdisc if parent class does not exist {CVE-2025-38457}
• misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() {CVE-2022-49788}
• dlm: fix plock invalid read {CVE-2022-49407}
• net: usb: smsc75xx: Limit packet length to skb->len {CVE-2023-53125}
• scsi: libfc: Fix use after free in fc_exch_abts_resp() {CVE-2022-49114}
• crypto: algif_hash - fix double free in hash_accept {CVE-2025-38079}
• HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556}
• HID: core: ensure the allocated report buffer can contain the reserved report ID {CVE-2025-38495}
• ext4: Fix possible corruption when moving a directory {CVE-2023-53137}
• ceph: avoid putting the realm twice when decoding snaps fails {CVE-2022-49770}
• vsock/vmci: Clear the vmci transport packet properly when initializing it {CVE-2025-38403}
• HID: core: do not bypass hid_hw_raw_request {CVE-2025-38494}
• sch_hfsc: make hfsc_qlen_notify() idempotent {CVE-2025-38177}
• ext4: check dot and dotdot of dx_root before making dir indexed {CVE-2024-42305}
• ALSA: bcd2000: Fix a UAF bug on the error path of probing {CVE-2022-50229}
• dm ioctl: prevent potential spectre v1 gadget {CVE-2022-49122}
• net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too {CVE-2025-37823}
• md-raid10: fix KASAN warning {CVE-2022-50211}
• scsi: lpfc: Use memcpy() for BIOS version {CVE-2025-38332}
• ACPICA: Refuse to evaluate a method if arguments are missing {CVE-2025-38386}
• media: cxusb: no longer judge rbuf when the write fails {CVE-2025-38229}
• ipc: fix to protect IPCS lookups using RCU {CVE-2025-38212}
• ext4: fix off-by-one error in do_split {CVE-2025-23150}
• perf/core: Fix WARN_ON(!ctx) in __free_event() for partial init {CVE-2025-37878}
• sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() {CVE-2025-38000}
• i40e: fix MMIO write access to an invalid page in i40e_clear_hw {CVE-2025-38200}

• x86/kvm: Disable kvmclock on all CPUs on shutdown {CVE-2021-47110}
• posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del() {CVE-2025-38352}
• cifs: fix double free race when mount fails in cifs_get_root() {CVE-2022-48919}
• aio: mark AIO pseudo-fs noexec {CVE-2016-10044}
• cifs: potential buffer overflow in handling symlinks {CVE-2022-49058}
• NFSD: fix race between nfsd registration and exports_proc {CVE-2025-38232}
• nfsd: register pernet ops last, unregister first {CVE-2025-38232}
• net: atm: fix use after free in lec_send() {CVE-2025-22004}
• net: atlantic: fix aq_vec index out of range error {CVE-2022-50066}
• do_change_type(): refuse to operate on unmounted/not ours mounts {CVE-2025-38498}
• net: atm: fix /proc/net/atm/lec handling {CVE-2025-38180}
• net: atm: add lec_mutex {CVE-2025-38180}
• SUNRPC: make sure cache entry active before cache_show {CVE-2024-53174}
• scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() {CVE-2025-38399}
• scsi: target: Fix crash during SPEC_I_PT handling {CVE-2025-38399}
• mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race {CVE-2025-38085}
• drivers:md:fix a potential use-after-free bug {CVE-2022-50022}
• ext4: avoid resizing to a partial cluster size {CVE-2022-50020}
• HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() {CVE-2025-21928}
• net/sched: Abort __tc_modify_qdisc if parent class does not exist {CVE-2025-38457}
• misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() {CVE-2022-49788}
• dlm: fix plock invalid read {CVE-2022-49407}
• net: usb: smsc75xx: Limit packet length to skb->len {CVE-2023-53125}
• scsi: libfc: Fix use after free in fc_exch_abts_resp() {CVE-2022-49114}
• crypto: algif_hash - fix double free in hash_accept {CVE-2025-38079}
• HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556}
• HID: core: ensure the allocated report buffer can contain the reserved report ID {CVE-2025-38495}
• ext4: Fix possible corruption when moving a directory {CVE-2023-53137}
• ceph: avoid putting the realm twice when decoding snaps fails {CVE-2022-49770}
• vsock/vmci: Clear the vmci transport packet properly when initializing it {CVE-2025-38403}
• HID: core: do not bypass hid_hw_raw_request {CVE-2025-38494}
• sch_hfsc: make hfsc_qlen_notify() idempotent {CVE-2025-38177}
• ext4: check dot and dotdot of dx_root before making dir indexed {CVE-2024-42305}
• ALSA: bcd2000: Fix a UAF bug on the error path of probing {CVE-2022-50229}
• dm ioctl: prevent potential spectre v1 gadget {CVE-2022-49122}
• net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too {CVE-2025-37823}
• md-raid10: fix KASAN warning {CVE-2022-50211}
• scsi: lpfc: Use memcpy() for BIOS version {CVE-2025-38332}
• ACPICA: Refuse to evaluate a method if arguments are missing {CVE-2025-38386}
• media: cxusb: no longer judge rbuf when the write fails {CVE-2025-38229}
• ipc: fix to protect IPCS lookups using RCU {CVE-2025-38212}
• ext4: fix off-by-one error in do_split {CVE-2025-23150}
• perf/core: Fix WARN_ON(!ctx) in __free_event() for partial init {CVE-2025-37878}
• sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() {CVE-2025-38000}
• i40e: fix MMIO write access to an invalid page in i40e_clear_hw {CVE-2025-38200}

• nfs: fix possible null-ptr-deref when parsing param {CVE-2022-50455}
• KVM: arm64: Disassociate vcpus from redistributor region on teardown {CVE-2024-40989}
• HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556}
• ALSA: usb-audio: Validate UAC3 cluster segment descriptors {CVE-2025-39757}
• tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg {CVE-2024-56633}
• ovl: Filter invalid inodes with missing lookup function {CVE-2024-56570}
• ACPI: processor: Check for null return of devm_kzalloc() in fch_misc_setup() {CVE-2023-53483}
• crypto: seqiv - Handle EBUSY correctly {CVE-2023-53373}
• KVM: nSVM: Check instead of asserting on nested TSC scaling support {CVE-2023-53663}
• ice: Don't tx before switchdev is fully configured {CVE-2023-53657}
• rcu: Avoid stack overflow due to __rcu_irq_enter_check_tick() being kprobe-ed {CVE-2023-53655}
• mm/swap: fix swap_info_struct race between swapoff and get_swap_pages() {CVE-2023-53623}
• ext4: fix bug_on in __es_tree_search caused by bad boot loader inode {CVE-2022-50485}
• ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode {CVE-2022-50485}
• ext4: add helper to check quota inums {CVE-2022-50485}
• ext4: fix bug_on in __es_tree_search caused by bad quota inode {CVE-2022-50485}
• swiotlb: Fix double-allocation of slots due to broken alignment handling {CVE-2024-35814}
• swiotlb: fix a braino in the alignment check fix {CVE-2024-35814}
• swiotlb: fix slot alignment checks {CVE-2024-35814}
• swiotlb: fix the deadlock in swiotlb_do_find_slots
• drm/radeon: free iio for atombios when driver shutdown {CVE-2023-53453}

• wifi: mwifiex: Fix OOB and integer underflow when rx packets {CVE-2023-53226} {CVE-2023-53226}
• wifi: mac80211: check S1G action frame size {CVE-2023-53257} {CVE-2023-53257}
• wifi: cfg80211: fix use-after-free in cmp_bss() {CVE-2025-39864} {CVE-2025-39864}
• partitions: mac: fix handling of bogus partition table {CVE-2025-21772} {CVE-2025-21772}
• wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() {CVE-2024-58014} {CVE-2024-58014}
• wifi: at76c50x: fix use after free access in at76_disconnect {CVE-2025-37796} {CVE-2025-37796}
• dma-direct: Leak pages on dma_set_decrypted() failure {CVE-2024-35939} {CVE-2024-35939}
• Bluetooth: L2CAP: Fix user-after-free {CVE-2022-50386} {CVE-2022-50386}
• efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare {CVE-2025-39817} {CVE-2025-39817}
• wifi: cfg80211: check A-MSDU format more carefully {CVE-2024-35937} {CVE-2024-35937}
• nfs: fix UAF in direct writes {CVE-2024-26958} {CVE-2024-26958}
• wifi: iwlwifi: mvm: guard against invalid STA ID on removal {CVE-2024-36921} {CVE-2024-36921}
• net/smc: avoid data corruption caused by decline {CVE-2023-52775} {CVE-2023-52775}
• bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() {CVE-2024-39487} {CVE-2024-39487}
• scsi: qedi: Fix crash while reading debugfs attribute {CVE-2024-40978} {CVE-2024-40978}
• mac802154: fix llsec key resources release in mac802154_llsec_key_del {CVE-2024-26961} {CVE-2024-26961}
• platform/x86: wmi: Fix opening of char device {CVE-2023-52864} {CVE-2023-52864}
• net/sched: act_mirred: don't override retval if we already lost the skb {CVE-2024-26739} {CVE-2024-26739}
• drm/dp_mst: Fix resetting msg rx state after topology removal {CVE-2024-57876} {CVE-2024-57876}
• net/mlx5: Add a timeout to acquire the command queue semaphore {CVE-2024-38556} {CVE-2024-38556}
• of: Fix double free in of_parse_phandle_with_args_map {CVE-2023-52679} {CVE-2023-52679}
• xhci: Handle TD clearing for multiple streams case {CVE-2024-40927} {CVE-2024-40927}
• wifi: mac80211: fix potential key use-after-free {CVE-2023-52530} {CVE-2023-52530}
• net: openvswitch: Fix Use-After-Free in ovs_ct_exit {CVE-2024-27395} {CVE-2024-27395}
• r8169: Fix possible ring buffer corruption on fragmented Tx packets. {CVE-2024-38586} {CVE-2024-38586}
• media: gspca: cpia1: shift-out-of-bounds in set_flicker {CVE-2023-52764} {CVE-2023-52764}
• media: bttv: fix use after free error due to btv->timeout timer {CVE-2023-52847} {CVE-2023-52847}
• vsock: Fix transport_* TOCTOU {CVE-2025-38461} {CVE-2025-38461}
• ppdev: Add an error check in register_device {CVE-2024-36015} {CVE-2024-36015}
• HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556} {CVE-2025-38556}
• iio: adc: at91: call input_free_device() on allocated iio_dev {CVE-2024-57904} {CVE-2024-57904}
• perf/aux: Fix AUX buffer serialization {CVE-2024-46713} {CVE-2024-46713}
• net_sched: hfsc: Fix a UAF vulnerability in class handling {CVE-2025-37797} {CVE-2025-37797}
• wifi: rtlwifi: remove unused check_buddy_priv {CVE-2024-58072} {CVE-2024-58072}
• wifi: rtlwifi: remove unused dualmac control leftovers {CVE-2024-58072} {CVE-2024-58072}
• wifi: rtlwifi: remove unused timer and related code {CVE-2024-58072} {CVE-2024-58072}
• ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all() {CVE-2025-22121} {CVE-2025-22121}
• ext4: move where set the MAY_INLINE_DATA flag is set {CVE-2025-22121} {CVE-2025-22121}
• ext4: introduce ITAIL helper {CVE-2025-22121} {CVE-2025-22121}
• ext4: improve xattr consistency checking and error reporting {CVE-2025-22121} {CVE-2025-22121}
• mm: fix zswap writeback race condition {CVE-2023-53178} {CVE-2023-53178}
• fs: fix UAF/GPF bug in nilfs_mdt_destroy {CVE-2022-50367} {CVE-2022-50367}
• ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control
• ALSA: usb-audio: Validate UAC3 cluster segment descriptors {CVE-2025-39757} {CVE-2025-39757}
• smb: client: fix use-after-free in cifs_oplock_break {CVE-2025-38527} {CVE-2025-38527} -…

• Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times {CVE-2022-50419}
• firewire: net: fix use after free in fwnet_finish_incoming_packet() {CVE-2023-53432}
• wifi: brcmfmac: fix use-after-free bug in brcmf_netdev_start_xmit() {CVE-2022-50408}
• wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() {CVE-2023-1380}
• wifi: mac80211_hwsim: drop short frames {CVE-2023-53321}
• wifi: cfg80211: Fix use after free for wext {CVE-2023-53153}
• scsi: libsas: Fix use-after-free bug in smp_execute_task_sg() {CVE-2022-50422}
• wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work {CVE-2025-39863}
• NFSD: Protect against send buffer overflow in NFSv2 READ {CVE-2022-43945}
• can: bcm: add locking for bcm_op runtime updates {CVE-2025-38004}
• Squashfs: check return result of sb_min_blocksize {CVE-2025-38415}
• scsi: qla2xxx: Wait for io return on terminate rport {CVE-2023-53322}
• fs: fix UAF/GPF bug in nilfs_mdt_destroy {CVE-2022-2978}
• ipv6: Fix infinite recursion in fib6_dump_done(). {CVE-2024-35886}
• wifi: ath9k_htc: Abort software beacon handling if disabled {CVE-2025-38157}
• atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). {CVE-2025-38245}
• atm: clip: Fix infinite recursive call of clip_push(). {CVE-2025-38459}
• smb: client: Fix use-after-free in cifs_fill_dirent {CVE-2025-38051}
• spec: merge oraclelinux6els changes
• ip6mr: Fix skb_under_panic in ip6mr_cache_report() {CVE-2023-53365}
• ipvs: fix WARNING in ip_vs_app_net_cleanup() {CVE-2022-49917}
• ipvs: fix WARNING in __ip_vs_cleanup_batch() {CVE-2022-49918}
• ipvs: use explicitly signed chars
• HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556}
• net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too {CVE-2025-37823}
• xen/netfront: react properly to failing gnttab_end_foreign_access_ref() {CVE-2022-48900}
• netlink: prevent potential spectre v1 gadgets {CVE-2023-53000}
• mtd: inftlcore: Add error check for inftl_read_oob() {CVE-2025-37892}
• igb: Do not free q_vector unless new one was allocated {CVE-2022-50252}
• scsi: target: Fix WRITE_SAME No Data Buffer crash {CVE-2022-21546}
• net: mdio: fix undefined behavior in bit shift for __mdiobus_register {CVE-2022-49907}
• capabilities: fix undefined behavior in bit shift for CAP_TO_MASK {CVE-2022-49870}
• wifi: brcmfmac: Fix potential stack-out-of-bounds in brcmf_c_preinit_dcmds() {CVE-2022-50258}
• md-raid10: fix KASAN warning {CVE-2022-50211}
• usb: xhci: Fix isochronous Ring Underrun/Overrun event handling {CVE-2025-37882}
• ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control {CVE-2025-39751}
• crypto: seqiv - Handle EBUSY correctly {CVE-2023-53373}
• wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() {CVE-2024-58014}
• isofs: Prevent the use of too small fid {CVE-2025-37780}
• net: openvswitch: fix nested key length validation in the set() action {CVE-2025-37789}
• partitions: mac: fix handling of bogus partition table {CVE-2025-21772}

• Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times {CVE-2022-50419}
• firewire: net: fix use after free in fwnet_finish_incoming_packet() {CVE-2023-53432}
• wifi: brcmfmac: fix use-after-free bug in brcmf_netdev_start_xmit() {CVE-2022-50408}
• wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies() {CVE-2023-1380}
• wifi: mac80211_hwsim: drop short frames {CVE-2023-53321}
• wifi: cfg80211: Fix use after free for wext {CVE-2023-53153}
• scsi: libsas: Fix use-after-free bug in smp_execute_task_sg() {CVE-2022-50422}
• wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work {CVE-2025-39863}
• NFSD: Protect against send buffer overflow in NFSv2 READ {CVE-2022-43945}
• can: bcm: add locking for bcm_op runtime updates {CVE-2025-38004}
• Squashfs: check return result of sb_min_blocksize {CVE-2025-38415}
• scsi: qla2xxx: Wait for io return on terminate rport {CVE-2023-53322}
• fs: fix UAF/GPF bug in nilfs_mdt_destroy {CVE-2022-2978}
• ipv6: Fix infinite recursion in fib6_dump_done(). {CVE-2024-35886}
• wifi: ath9k_htc: Abort software beacon handling if disabled {CVE-2025-38157}
• atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). {CVE-2025-38245}
• atm: clip: Fix infinite recursive call of clip_push(). {CVE-2025-38459}
• smb: client: Fix use-after-free in cifs_fill_dirent {CVE-2025-38051}
• spec: merge oraclelinux6els changes
• ip6mr: Fix skb_under_panic in ip6mr_cache_report() {CVE-2023-53365}
• ipvs: fix WARNING in ip_vs_app_net_cleanup() {CVE-2022-49917}
• ipvs: fix WARNING in __ip_vs_cleanup_batch() {CVE-2022-49918}
• ipvs: use explicitly signed chars
• HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556}
• net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too {CVE-2025-37823}
• xen/netfront: react properly to failing gnttab_end_foreign_access_ref() {CVE-2022-48900}
• netlink: prevent potential spectre v1 gadgets {CVE-2023-53000}
• mtd: inftlcore: Add error check for inftl_read_oob() {CVE-2025-37892}
• igb: Do not free q_vector unless new one was allocated {CVE-2022-50252}
• scsi: target: Fix WRITE_SAME No Data Buffer crash {CVE-2022-21546}
• net: mdio: fix undefined behavior in bit shift for __mdiobus_register {CVE-2022-49907}
• capabilities: fix undefined behavior in bit shift for CAP_TO_MASK {CVE-2022-49870}
• wifi: brcmfmac: Fix potential stack-out-of-bounds in brcmf_c_preinit_dcmds() {CVE-2022-50258}
• md-raid10: fix KASAN warning {CVE-2022-50211}
• usb: xhci: Fix isochronous Ring Underrun/Overrun event handling {CVE-2025-37882}
• ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control {CVE-2025-39751}
• crypto: seqiv - Handle EBUSY correctly {CVE-2023-53373}
• wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() {CVE-2024-58014}
• isofs: Prevent the use of too small fid {CVE-2025-37780}
• net: openvswitch: fix nested key length validation in the set() action {CVE-2025-37789}
• partitions: mac: fix handling of bogus partition table {CVE-2025-21772}

• net/ieee802154: don't warn zero-sized raw_sendmsg() {CVE-2022-50706}
• bpf: Don't redirect packets with invalid pkt_len {CVE-2022-49975}
• media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() {CVE-2025-38680}
• ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network {CVE-2022-49865}
• scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() {CVE-2023-53676}
• ring-buffer: Fix deadloop issue on reading trace_pipe {CVE-2023-53668}
• binfmt_misc: fix shift-out-of-bounds in check_special_flags {CVE-2022-50497}
• ALSA: usb-audio: Fix potential overflow of PCM transfer buffer {CVE-2025-40269}
• NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid {CVE-2025-68349}
• 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 potential buffer overflow in do_register_framebuffer() {CVE-2025-38702}
• i40e: Fix potential invalid access when MAC list is empty {CVE-2025-39853}
• fs/buffer: fix use-after-free when call bh_read() helper {CVE-2025-39691}
• wifi: iwlwifi: mvm: fix double list_add at iwl_mvm_mac_wake_tx_queue {CVE-2022-50164}
• mptcp: fix race condition in mptcp_schedule_work() {CVE-2025-40258}
• fbdev: bitblit: bound-check glyph index in bit_putcs* {CVE-2025-40322}
• smb: client: Fix use-after-free in cifs_fill_dirent {CVE-2025-38051}
• net: atm: fix /proc/net/atm/lec handling {CVE-2025-38180}
• HID: intel-ish-hid: ipc: Fix potential use-after-free in work function {CVE-2023-53039}
• Bluetooth: L2CAP: Fix use-after-free {CVE-2023-53305}
• wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work {CVE-2025-39863}
• sched, cpuset: Fix dl_cpu_busy() panic due to empty cs->cpus_allowed {CVE-2022-50103}
• nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() {CVE-2025-38724}
• xfrm: Duplicate SPI Handling {CVE-2025-39797}
• scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input {CVE-2022-50030}
• net/mlx5e: IPoIB, Block PKEY interfaces with less rx queues than parent {CVE-2022-48883}
• net/mlx5e: Move representor neigh cleanup to profile cleanup_tx {CVE-2023-54148}
• dm raid: fix address sanitizer warning in raid_resume {CVE-2022-50085}
• Squashfs: check the inode number is not the invalid value of zero {CVE-2024-26982}
• ASoC: SOF: Intel: hda: Fix potential buffer overflow by snprintf() {CVE-2022-50050}
• platform/x86: wmi: Fix opening of char device {CVE-2023-52864}
• nfs: fix UAF in direct writes {CVE-2024-26958}
• iomap: iomap: fix memory corruption when recording errors during writeback {CVE-2022-50406}
• drm/amdkfd: Fix an illegal memory access {CVE-2023-53090}
• HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556}
• scsi: target: Fix WRITE_SAME No Data Buffer crash {CVE-2022-21546}
• ALSA: pcm: Fix potential data race at PCM memory allocation helpers {CVE-2023-54072}
• drm/amd/display: fix shift-out-of-bounds in CalculateVMAndRowBytes {CVE-2023-53077}
• net: bridge: use DEV_STATS_INC() {CVE-2023-52578}
• i40e: fix idx validation in config queues msg {CVE-2025-39971}
• loop: Fix use-after-free issues {CVE-2023-53111}
• fs: prevent out-of-bounds array speculation when closing a file descriptor {CVE-2023-53117}
• media: rc: fix races with imon_disconnect() {CVE-2025-39993}
• fbcon: Make sure modelist not set on unregistered console {CVE-2025-38198}
• vsock: Ignore signal/timeout on connect() if already established {CVE-2025-40248}
• Bluetooth: hci_event: call disconnect callback before deleting conn {CVE-2023-53673}
• wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus() {CVE-2023-52594}
• pid: take a reference when initializing cad_pid {CVE-2021-47118}
• net: ppp: Add bound checking for skb data on ppp_sync_txmung {CVE-2025-37749}
• iommu/amd: Fix potential buffer overflow in…

• net/ieee802154: don't warn zero-sized raw_sendmsg() {CVE-2022-50706}
• scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() {CVE-2023-53676}
• ALSA: usb-audio: Fix potential overflow of PCM transfer buffer {CVE-2025-40269}
• ipv6: reject malicious packets in ipv6_gso_segment() {CVE-2025-38572}
• smb: client: Fix use-after-free in cifs_fill_dirent {CVE-2025-38051}
• net: atm: fix /proc/net/atm/lec handling {CVE-2025-38180}
• HID: intel-ish-hid: ipc: Fix potential use-after-free in work function {CVE-2023-53039}
• Bluetooth: L2CAP: Fix use-after-free {CVE-2023-53305}
• wifi: brcmfmac: fix use-after-free when rescheduling brcmf_btcoex_info work {CVE-2025-39863}
• sched, cpuset: Fix dl_cpu_busy() panic due to empty cs->cpus_allowed {CVE-2022-50103}
• nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() {CVE-2025-38724}
• xfrm: Duplicate SPI Handling {CVE-2025-39797}
• scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input {CVE-2022-50030}
• net/mlx5e: IPoIB, Block PKEY interfaces with less rx queues than parent {CVE-2022-48883}
• net/mlx5e: Move representor neigh cleanup to profile cleanup_tx {CVE-2023-54148}
• dm raid: fix address sanitizer warning in raid_resume {CVE-2022-50085}
• ASoC: SOF: Intel: hda: Fix potential buffer overflow by snprintf() {CVE-2022-50050}
• nfs: fix UAF in direct writes {CVE-2024-26958}
• iomap: iomap: fix memory corruption when recording errors during writeback {CVE-2022-50406}
• drm/amdkfd: Fix an illegal memory access {CVE-2023-53090}
• scsi: target: Fix WRITE_SAME No Data Buffer crash {CVE-2022-21546}
• ALSA: pcm: Fix potential data race at PCM memory allocation helpers {CVE-2023-54072}
• drm/amd/display: fix shift-out-of-bounds in CalculateVMAndRowBytes {CVE-2023-53077}
• net: bridge: use DEV_STATS_INC() {CVE-2023-52578}
• loop: Fix use-after-free issues {CVE-2023-53111}
• media: rc: fix races with imon_disconnect() {CVE-2025-39993}
• fbcon: Make sure modelist not set on unregistered console {CVE-2025-38198}
• vsock: Ignore signal/timeout on connect() if already established {CVE-2025-40248}
• Bluetooth: hci_event: call disconnect callback before deleting conn {CVE-2023-53673}
• ALSA: usb-audio: Validate UAC3 power domain descriptors, too {CVE-2025-38729}
• libceph: fix potential use-after-free in have_mon_and_osd_map() {CVE-2025-68285}
• firewire: net: fix use after free in fwnet_finish_incoming_packet() {CVE-2023-53432}
• tracing: Fix wild-memory-access in register_synth_event() {CVE-2022-49799}
• iommu/vt-d: avoid invalid memory access via node_online(NUMA_NO_NODE) {CVE-2022-50093}
• drm/shmem-helper: Remove another errant put in error path {CVE-2023-53084}
• wifi: mac80211: Fix UAF in ieee80211_scan_rx() {CVE-2022-49934}
• drm/radeon: fix potential buffer overflow in ni_set_mc_special_registers() {CVE-2022-50185}
• ext4: fix undefined behavior in bit shift for ext4_check_flag_values {CVE-2022-50403}
• wifi: rtlwifi: Fix global-out-of-bounds bug in _rtl8812ae_phy_set_txpower_limit() {CVE-2022-50279}
• nbd: fix incomplete validation of ioctl arg {CVE-2023-53513}
• r8169: Fix possible ring buffer corruption on fragmented Tx packets. {CVE-2024-38586}
• sctp: handle the error returned from sctp_auth_asoc_init_active_key {CVE-2022-50243}
• crypto: qat - resolve race condition during AER recovery {CVE-2024-39493}
• i40e: fix idx validation in config queues msg {CVE-2025-39971}
• netfilter: nf_tables: prefer nft_chain_validate {CVE-2024-41042}
• platform/x86: wmi: Fix opening of char device {CVE-2023-52864}
• netfilter: validate user input for expected length {CVE-2024-35962}
• wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus() {CVE-2023-52594}
• Squashfs: check the inode number is not the invalid value of zero {CVE-2024-26982}
• wifi: iwlwifi: fix a memory corruption {CVE-2024-26610}
• pid: take a reference when initializing cad_pid {CVE-2021-47118}
• wifi: cfg80211: check A-MSDU format more carefully…

• ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() {CVE-2026-23089}
• HID: core: Harden s32ton() against conversion to 0 bits {CVE-2025-38556}
• KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory {CVE-2024-50115}
• KVM: x86: Reset IRTE to host control if new route isn't postable {CVE-2025-37885}
• NFSD: Protect against send buffer overflow in NFSv2 READ {CVE-2022-43945}
• NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid {CVE-2025-68349}
• Revert "IB/core: Implement clear counters"
• Revert "IB/mlx5: Implement clear counters"
• Revert "ib/core: add SET_DEVICE_OP call for clear_hw_stats()"
• Revert "perf/x86: Always store regs->ip in perf_callchain_kernel()"
• Revert "xfrm: destroy xfrm_state synchronously on net exit path"
• bpf, sockmap: Fix race between element replace and close() {CVE-2024-56664}
• can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak {CVE-2026-23061}
• crypto: authencesn - reject too-short AAD (assoclen<8) to match ESP/ESN spec {CVE-2026-23060}
• crypto: lzo - Fix compression buffer overrun {CVE-2025-38068}
• drm/amd/pm: fix the Out-of-bounds read warning {CVE-2024-46731}
• drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number {CVE-2024-46724}
• drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer {CVE-2024-49991}
• ext4/jbd2: skip sb flush when EIO happened
• ext4: save the error code which triggered an
• fou: remove warn in gue_gro_receive on unsupported protocol {CVE-2024-44940}
• fs: proc: inode: delay put_pid() by RCU
• fs: writeback: fix use-after-free in __mark_inode_dirty() {CVE-2025-39866}
• genirq/cpuhotplug: Notify about affinity changes breaking the affinity mask
• io_uring: fix filename leak in __io_openat_prep() {CVE-2025-68814}
• jbd2: store more accurate errno in superblock
• libceph: fix potential use-after-free in have_mon_and_osd_map() {CVE-2025-68285}
• libceph: make free_choose_arg_map() resilient to partial allocation {CVE-2026-22991}
• macvlan: Add nodst option to macvlan type source
• macvlan: Use 'hash' iterators to simplify code
• macvlan: fix error recovery in macvlan_common_newlink() {CVE-2026-23209}
• macvlan: fix possible UAF in macvlan_forward_source() {CVE-2026-23001}
• macvlan: observe an RCU grace period in macvlan_common_newlink() error path {CVE-2026-23273}
• media: xc2028: avoid use-after-free in load_firmware_cb() {CVE-2024-43900}
• mm: call the security_mmap_file() LSM hook in remap_file_pages() {CVE-2024-47745}
• net/sched: sch_qfq: do not free existing class in qfq_change_class() {CVE-2026-22999}
• net: sock: fix hardened usercopy panic in sock_recv_errqueue {CVE-2026-22977}
• net: usb: rtl8150: fix memory leak on usb_submit_urb() failure {CVE-2025-71154}
• rds: Add state field to RDS trace logs.
• rds: Drop rds conn in connect worker if not in down state.
• scsi: mpi3mr: Sanitise num_phys {CVE-2024-42159}
• scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() {CVE-2026-23193}
• tty: n_gsm: Fix use-after-free in gsm_cleanup_mux {CVE-2024-50073}
• usb: core: config: Prevent OOB read in SS endpoint companion parsing {CVE-2025-39760}
• vhost-scsi: Fix handling of multiple calls to vhost_scsi_set_endpoint {CVE-2025-22083}
• wifi: iwlwifi: mvm: check n_ssids before accessing the ssids {CVE-2024-40929}
• xfrm: also call xfrm_state_delete_tunnel at destroy time for states that were never added {CVE-2025-40256}
• xfrm: delete x->tunnel as we delete x {CVE-2025-40215}
• xfrm: flush all states in xfrm_state_fini

• Rebased onto Oracle UEK base 5.4.17-2136.357.2.el7uek
• sctp: don't free the ASCONF's own transport in DEL-IP processing {CVE-2026-64564}
• ocfs2/dlm: fix off-by-one in dlm_match_regions() region comparison {CVE-2026-53309}
• ocfs2/dlm: validate qr_numregions in dlm_match_regions() {CVE-2026-53043}
• ixgbevf: fix use-after-free in VEPA multicast source pruning {CVE-2026-64113}
• ipv4: raw: reject IP_HDRINCL packets with ihl < 5 {CVE-2026-64114}
• NFSv4: include MAY_WRITE in open permission mask for O_TRUNC {CVE-2026-64298}
• fuse: re-lock request before returning from fuse_ref_folio() {CVE-2026-64266}
• scsi: isci: Fix use-after-free in device removal path {CVE-2026-64103}
• crypto: authencesn - reject too-short AAD (assoclen<8) to match ESP/ESN spec {CVE-2026-23060}
• futex/requeue: Prevent NULL pointer dereference in remove_waiter() on self-deadlock {CVE-2026-53166}
• net: af_key: zero aligned sockaddr tail in PF_KEY exports {CVE-2026-43088}
• scsi: aic94xx: fix use-after-free in device removal path {CVE-2025-71075}
• i2c: piix4: Fix adapter not be removed in piix4_remove() {CVE-2022-49900}
• Bluetooth: MGMT: validate LTK enc_size on load {CVE-2026-43020}
• ext4: convert inline data to extents when truncate exceeds inline size {CVE-2026-31452}
• can: raw: fix ro->uniq use-after-free in raw_rcv() {CVE-2026-31532}
• ALSA: 6fire: fix use-after-free on disconnect {CVE-2026-31581}
• ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY {CVE-2026-31597}
• netfilter: nf_conntrack_helper: pass helper to expect cleanup {CVE-2026-43027}
• drm/amdgpu: Fix use-after-free race in VM acquire {CVE-2026-43370}
• xfrm_user: fix info leak in build_mapping() {CVE-2026-43089}
• xfs: fix freemap adjustments when adding xattrs to leaf blocks {CVE-2026-43158}
• libceph: make decode_pool() more resilient against corrupted osdmaps {CVE-2025-71116}
• e1000: fix OOB in e1000_tbi_should_accept() {CVE-2025-71093}
• ALSA: usb-audio: Use correct version for UAC3 header validation {CVE-2026-23318}
• nfnetlink_osf: validate individual option lengths in fingerprints {CVE-2026-23397}
• Squashfs: check metadata block offset is within range {CVE-2026-23388}
• net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled {CVE-2026-23381}
• wifi: mac80211: fix NULL deref in mesh_matches_local() {CVE-2026-23396}
• icmp: fix NULL pointer dereference in icmp_tag_validation() {CVE-2026-23398}
• HID: Add HID_CLAIMED_INPUT guards in raw_event callbacks missing them {CVE-2026-23382}
• net: usb: kalmia: validate USB endpoints {CVE-2026-23365}
• wifi: radiotap: reject radiotap with unknown bits {CVE-2026-23367}
• drbd: fix "LOGIC BUG" in drbd_al_begin_io_nonblock() {CVE-2026-23356}
• batman-adv: reject oversized global TT response buffers {CVE-2026-31659}
• drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set() {CVE-2026-43206}
• net: ipv6: ndisc: fix ndisc_ra_useropt to initialize nduseropt_padX fields to zero to prevent an info-leak {CVE-2026-43040}
• ALSA: ctxfi: Limit PTP to a single page {CVE-2026-31602}
• nvdimm/bus: Fix potential use after free in asynchronous initialization {CVE-2026-31399}
• usb: class: cdc-wdm: fix reordering issue in read code path {CVE-2026-43427}
• media: dvb-net: fix OOB access in ULE extension header tables {CVE-2026-31405}
• sysctl: Fix data races in proc_douintvec(). {CVE-2022-49641}
• netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() {CVE-2026-43450}
• ALSA: caiaq: fix stack out-of-bounds read in init_card {CVE-2026-31778}
• atm: lec: fix use-after-free in sock_def_readable() {CVE-2026-43050}
• fs: writeback: fix use-after-free in __mark_inode_dirty() {CVE-2025-39866}
• usb: core: config: Prevent OOB read in SS endpoint companion parsing {CVE-2025-39760}
• crypto: lzo - Fix compression buffer overrun {CVE-2025-38068}
• KVM: x86: Reset IRTE to host control if new route isn't postable {CVE-2025-37885}
• vhost-scsi: Fix handling of multiple calls to vhost_scsi_set_endpoint {CVE-2025-22083}
• mm:…

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

HID: core: Harden s32ton() against conversion to 0 bits

Testing by the syzbot fuzzer showed that the HID core gets a shift-out-of-bounds exception when it tries to convert a 32-bit quantity to a 0-bit quantity. Ideally this should never occur, but there are buggy devices and some might have a report field with size set to zero; we shouldn't reject the report or the device just because of that.

Instead, harden the s32ton() routine so that it returns a reasonable result instead of crashing when it is called with the number of bits set to 0 -- the same as what snto32() does.

The SUSE Linux Enterprise Server 16.0 and SUSE Linux Micro 6.2 kernel was updated to receive various security bugfixes.

The following security bugs were fixed:

• CVE-2024-53164: net: sched: fix ordering of qlen adjustment (bsc#1234863).
• CVE-2024-57891: sched_ext: Fix invalid irq restore in scx_ops_bypass() (bsc#1235953).
• CVE-2024-57951: hrtimers: Handle CPU state correctly on hotplug (bsc#1237108).
• CVE-2024-57952: Revert "libfs: fix infinite directory reads for offset dir" (bsc#1237131).
• CVE-2024-58090: sched/core: Prevent rescheduling when interrupts are disabled (bsc#1240324).
• CVE-2025-22034: mm/rmap: avoid -EBUSY from make_device_exclusive() (bsc#1241435).
• CVE-2025-22077: Revert "smb: client: fix TCP timers deadlock after rmmod" (bsc#1241403).
• CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses (bsc#1242782).
• CVE-2025-37821: sched/eevdf: Fix se->slice being set to U64_MAX and resulting (bsc#1242864).
• CVE-2025-37849: KVM: arm64: Tear down vGIC on failed vCPU creation (bsc#1243000).
• CVE-2025-37856: btrfs: harden block_group::bg_list against list_del() races (bsc#1243068).
• CVE-2025-37861: scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue (bsc#1243055).
• CVE-2025-37864: net: dsa: clean up FDB, MDB, VLAN entries on unbind (bsc#1242965).
• CVE-2025-38006: net: mctp: Do not access ifa_index when missing (bsc#1244930).
• CVE-2025-38008: mm/page_alloc: fix race condition in unaccepted memory handling (bsc#1244939).
• CVE-2025-38019: mlxsw: spectrum_router: Fix use-after-free when deleting GRE net devices (bsc#1245000).
• CVE-2025-38034: btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (bsc#1244792).
• CVE-2025-38038: cpufreq: amd-pstate: Remove unnecessary driver_lock in set_boost (bsc#1244812).
• CVE-2025-38058: __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (bsc#1245151).
• CVE-2025-38062: kABI: restore layout of struct msi_desc (bsc#1245216).
• CVE-2025-38075: scsi: target: iscsi: Fix timeout on deleted connection (bsc#1244734).
• CVE-2025-38101: ring-buffer: Fix buffer locking in ring_buffer_subbuf_order_set() (bsc#1245659).
• CVE-2025-38103: HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() (bsc#1245663).
• CVE-2025-38106: io_uring/sqpoll: do not put task_struct on tctx setup failure (bsc#1245664).
• CVE-2025-38117: hci_dev centralize extra lock (bsc#1245695).
• CVE-2025-38119: scsi: core: ufs: Fix a hang in the error handler (bsc#1245700).
• CVE-2025-38125: net: stmmac: make sure that ptp_rate is not 0 before configuring EST (bsc#1245710).
• CVE-2025-38146: net: openvswitch: Fix the dead loop of MPLS parse (bsc#1245767).
• CVE-2025-38160: clk: bcm: rpi: Add NULL check in raspberrypi_clk_register() (bsc#1245780).
• CVE-2025-38168: perf: arm-ni: Unregister PMUs on probe failure (bsc#1245763).
• CVE-2025-38180: net: atm: fix /proc/net/atm/lec handling (bsc#1245970).
• CVE-2025-38182: ublk: santizize the arguments from userspace when adding a device (bsc#1245937).
• CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer (bsc#1245956).
• CVE-2025-38185: atm: atmtcp: Free invalid length skb in atmtcp_c_send() (bsc#1246012).
• CVE-2025-38190: atm: Revert atm_account_tx() if copy_from_iter_full() fails (bsc#1245973).
• CVE-2025-38201: netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX (bsc#1245977).
• CVE-2025-38205: drm/amd/display: Avoid divide by zero by initializing dummy pitch to 1 (bsc#1246005).
• CVE-2025-38208: smb: client: add NULL check in automount_fullpath (bsc#1245815).
• CVE-2025-38216: iommu/vt-d: Restore context entry setup order for aliased devices (bsc#1245963).
• CVE-2025-38220: ext4: only dirty folios when data journaling regular files (bsc#1245966).
• CVE-2025-38222: ext4: inline: fix len overflow in ext4_prepare_inline_data (bsc#1245976).
• CVE-2025-38242: mm: userfaultfd: fix race of userfaultfd_move and swap…