CVE-2025-68349

In the Linux kernel, the following vulnerability has been resolved: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid Fixes a crash when layout is null during this call stack: write_inode -> nfs4_write_inode -> pnfs_layoutcommit_inode pnfs_set_layoutcommit relies on the lseg refcount to keep the layout around. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt to reference a null layout.

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction

The commit 59c68ac31e15 ("iw_cm: free cm_id resources on the last deref") simplified cm_id resource management by freeing cm_id once all references to the cm_id were removed. The references are removed either upon completion of iw_cm event handlers or when the application destroys the cm_id. This commit introduced the use-after-free condition where cm_id_private object could still be in use by event handler works during the destruction of cm_id. The commit aee2424246f9 ("RDMA/iwcm: Fix a use-after-free related to destroying CM IDs") addressed this use-after- free by flushing all pending works at the cm_id destruction.

However, still another use-after-free possibility remained. It happens with the work objects allocated for each cm_id_priv within alloc_work_entries() during cm_id creation, and subsequently freed in dealloc_work_entries() once all references to the cm_id are removed. If the cm_id's last reference is decremented in the event handler work, the work object for the work itself gets removed, and causes the use- after-free BUG below:

BUG: KASAN: slab-use-after-free in __pwq_activate_work+0x1ff/0x250 Read of size 8 at addr ffff88811f9cf800 by task kworker/u16:1/147091

CPU: 2 UID: 0 PID: 147091 Comm: kworker/u16:1 Not tainted 6.15.0-rc2+ #27 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014 Workqueue: 0x0 (iw_cm_wq) Call Trace: <TASK> dump_stack_lvl+0x6a/0x90 print_report+0x174/0x554 ? __virt_addr_valid+0x208/0x430 ? __pwq_activate_work+0x1ff/0x250 kasan_report+0xae/0x170 ? __pwq_activate_work+0x1ff/0x250 __pwq_activate_work+0x1ff/0x250 pwq_dec_nr_in_flight+0x8c5/0xfb0 process_one_work+0xc11/0x1460 ? __pfx_process_one_work+0x10/0x10 ? assign_work+0x16c/0x240 worker_thread+0x5ef/0xfd0 ? __pfx_worker_thread+0x10/0x10 kthread+0x3b0/0x770 ? __pfx_kthread+0x10/0x10 ? rcu_is_watching+0x11/0xb0 ? _raw_spin_unlock_irq+0x24/0x50 ? rcu_is_watching+0x11/0xb0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x30/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK>

Allocated by task 147416: kasan_save_stack+0x2c/0x50 kasan_save_track+0x10/0x30 __kasan_kmalloc+0xa6/0xb0 alloc_work_entries+0xa9/0x260 [iw_cm] iw_cm_connect+0x23/0x4a0 [iw_cm] rdma_connect_locked+0xbfd/0x1920 [rdma_cm] nvme_rdma_cm_handler+0x8e5/0x1b60 [nvme_rdma] cma_cm_event_handler+0xae/0x320 [rdma_cm] cma_work_handler+0x106/0x1b0 [rdma_cm] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30

Freed by task 147091: kasan_save_stack+0x2c/0x50 kasan_save_track+0x10/0x30 kasan_save_free_info+0x37/0x60 __kasan_slab_free+0x4b/0x70 kfree+0x13a/0x4b0 dealloc_work_entries+0x125/0x1f0 [iw_cm] iwcm_deref_id+0x6f/0xa0 [iw_cm] cm_work_handler+0x136/0x1ba0 [iw_cm] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30

Last potentially related work creation: kasan_save_stack+0x2c/0x50 kasan_record_aux_stack+0xa3/0xb0 __queue_work+0x2ff/0x1390 queue_work_on+0x67/0xc0 cm_event_handler+0x46a/0x820 [iw_cm] siw_cm_upcall+0x330/0x650 [siw] siw_cm_work_handler+0x6b9/0x2b20 [siw] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30

This BUG is reproducible by repeating the blktests test case nvme/061 for the rdma transport and the siw driver.

To avoid the use-after-free of cm_id_private work objects, ensure that the last reference to the cm_id is…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction

The commit 59c68ac31e15 ("iw_cm: free cm_id resources on the last deref") simplified cm_id resource management by freeing cm_id once all references to the cm_id were removed. The references are removed either upon completion of iw_cm event handlers or when the application destroys the cm_id. This commit introduced the use-after-free condition where cm_id_private object could still be in use by event handler works during the destruction of cm_id. The commit aee2424246f9 ("RDMA/iwcm: Fix a use-after-free related to destroying CM IDs") addressed this use-after- free by flushing all pending works at the cm_id destruction.

However, still another use-after-free possibility remained. It happens with the work objects allocated for each cm_id_priv within alloc_work_entries() during cm_id creation, and subsequently freed in dealloc_work_entries() once all references to the cm_id are removed. If the cm_id's last reference is decremented in the event handler work, the work object for the work itself gets removed, and causes the use- after-free BUG below:

BUG: KASAN: slab-use-after-free in __pwq_activate_work+0x1ff/0x250 Read of size 8 at addr ffff88811f9cf800 by task kworker/u16:1/147091

CPU: 2 UID: 0 PID: 147091 Comm: kworker/u16:1 Not tainted 6.15.0-rc2+ #27 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014 Workqueue: 0x0 (iw_cm_wq) Call Trace: <TASK> dump_stack_lvl+0x6a/0x90 print_report+0x174/0x554 ? __virt_addr_valid+0x208/0x430 ? __pwq_activate_work+0x1ff/0x250 kasan_report+0xae/0x170 ? __pwq_activate_work+0x1ff/0x250 __pwq_activate_work+0x1ff/0x250 pwq_dec_nr_in_flight+0x8c5/0xfb0 process_one_work+0xc11/0x1460 ? __pfx_process_one_work+0x10/0x10 ? assign_work+0x16c/0x240 worker_thread+0x5ef/0xfd0 ? __pfx_worker_thread+0x10/0x10 kthread+0x3b0/0x770 ? __pfx_kthread+0x10/0x10 ? rcu_is_watching+0x11/0xb0 ? _raw_spin_unlock_irq+0x24/0x50 ? rcu_is_watching+0x11/0xb0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x30/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK>

Allocated by task 147416: kasan_save_stack+0x2c/0x50 kasan_save_track+0x10/0x30 __kasan_kmalloc+0xa6/0xb0 alloc_work_entries+0xa9/0x260 [iw_cm] iw_cm_connect+0x23/0x4a0 [iw_cm] rdma_connect_locked+0xbfd/0x1920 [rdma_cm] nvme_rdma_cm_handler+0x8e5/0x1b60 [nvme_rdma] cma_cm_event_handler+0xae/0x320 [rdma_cm] cma_work_handler+0x106/0x1b0 [rdma_cm] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30

Freed by task 147091: kasan_save_stack+0x2c/0x50 kasan_save_track+0x10/0x30 kasan_save_free_info+0x37/0x60 __kasan_slab_free+0x4b/0x70 kfree+0x13a/0x4b0 dealloc_work_entries+0x125/0x1f0 [iw_cm] iwcm_deref_id+0x6f/0xa0 [iw_cm] cm_work_handler+0x136/0x1ba0 [iw_cm] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30

Last potentially related work creation: kasan_save_stack+0x2c/0x50 kasan_record_aux_stack+0xa3/0xb0 __queue_work+0x2ff/0x1390 queue_work_on+0x67/0xc0 cm_event_handler+0x46a/0x820 [iw_cm] siw_cm_upcall+0x330/0x650 [siw] siw_cm_work_handler+0x6b9/0x2b20 [siw] process_one_work+0x84f/0x1460 worker_thread+0x5ef/0xfd0 kthread+0x3b0/0x770 ret_from_fork+0x30/0x70 ret_from_fork_asm+0x1a/0x30

This BUG is reproducible by repeating the blktests test case nvme/061 for the rdma transport and the siw driver.

To avoid the use-after-free of cm_id_private work objects, ensure that the last reference to the cm_id is…

The Linux Kernel, the operating system core itself.

Security Fix(es):

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

NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid

Fixes a crash when layout is null during this call stack:

write_inode -> nfs4_write_inode -> pnfs_layoutcommit_inode

pnfs_set_layoutcommit relies on the lseg refcount to keep the layout around. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt to reference a null layout.(CVE-2025-68349)

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/vmci: Clear the vmci transport packet properly when initializing it (CVE-2025-38403)

• 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 ALSA USB audio driver: Buffer overflow leading to information disclosure and denial of service (CVE-2025-40269)

• kernel: ext4: fix use-after-free in ext4_orphan_cleanup (CVE-2022-50673)

• kernel: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (CVE-2025-68349)

• kernel: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (CVE-2026-22998)

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: ntb_hw_switchtec: Fix shift-out-of-bounds in switchtec_ntb_mw_set_trans (CVE-2023-53034)

• kernel: Linux kernel erofs: Use-After-Free due to device type mismatch (CVE-2025-38172)

• kernel: smc: Fix use-after-free in __pnet_find_base_ndev() (CVE-2025-40064)

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

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

• kernel: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (CVE-2025-68349)

• kernel: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (CVE-2026-22998)

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: ntb_hw_switchtec: Fix shift-out-of-bounds in switchtec_ntb_mw_set_trans (CVE-2023-53034)

• kernel: smc: Fix use-after-free in __pnet_find_base_ndev() (CVE-2025-40064)

• kernel: Linux kernel: Out-of-bounds write in fbdev can lead to privilege escalation, information disclosure, or denial of service. (CVE-2025-40304)

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

• kernel: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (CVE-2025-68349)

• kernel: svcrdma: use rc_pageoff for memcpy byte offset (CVE-2025-68811)

• kernel: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (CVE-2026-22998)

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-68349 in the linux package for Root:Debian:11. Multiple fixed versions available.

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

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

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

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

In the Linux kernel, the following vulnerability has been resolved: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid Fixes a crash when layout is null during this call stack: write_inode -> nfs4_write_inode -> pnfs_layoutcommit_inode pnfs_set_layoutcommit relies on the lseg refcount to keep the layout around. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt to reference a null layout.

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

Security Fix(es):

• kernel: vsock/vmci: Clear the vmci transport packet properly when initializing it (CVE-2025-38403)
• 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 ALSA USB audio driver: Buffer overflow leading to information disclosure and denial of service (CVE-2025-40269)
• kernel: ext4: fix use-after-free in ext4_orphan_cleanup (CVE-2022-50673)
• kernel: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (CVE-2025-68349)
• kernel: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (CVE-2026-22998)

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-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.

Security Fix(es):

• kernel: vsock/vmci: Clear the vmci transport packet properly when initializing it (CVE-2025-38403)
• 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 ALSA USB audio driver: Buffer overflow leading to information disclosure and denial of service (CVE-2025-40269)
• kernel: ext4: fix use-after-free in ext4_orphan_cleanup (CVE-2022-50673)
• kernel: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (CVE-2025-68349)
• kernel: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (CVE-2026-22998)

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: ntb_hw_switchtec: Fix shift-out-of-bounds in switchtec_ntb_mw_set_trans (CVE-2023-53034)
• kernel: Linux kernel erofs: Use-After-Free due to device type mismatch (CVE-2025-38172)
• kernel: smc: Fix use-after-free in __pnet_find_base_ndev() (CVE-2025-40064)
• kernel: Bluetooth: ISO: Fix possible UAF on iso_conn_free (CVE-2025-40141)
• kernel: Linux kernel ALSA USB audio driver: Buffer overflow leading to information disclosure and denial of service (CVE-2025-40269)
• kernel: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (CVE-2025-68349)
• kernel: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (CVE-2026-22998)

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: ntb_hw_switchtec: Fix shift-out-of-bounds in switchtec_ntb_mw_set_trans (CVE-2023-53034)
• kernel: smc: Fix use-after-free in __pnet_find_base_ndev() (CVE-2025-40064)
• kernel: Linux kernel: Out-of-bounds write in fbdev can lead to privilege escalation, information disclosure, or denial of service. (CVE-2025-40304)
• kernel: Linux kernel: Information disclosure and denial of service via out-of-bounds read in font glyph handling (CVE-2025-40322)
• kernel: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (CVE-2025-68349)
• kernel: svcrdma: use rc_pageoff for memcpy byte offset (CVE-2025-68811)
• kernel: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (CVE-2026-22998)

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:

NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid

Fixes a crash when layout is null during this call stack:

write_inode -> nfs4_write_inode -> pnfs_layoutcommit_inode

pnfs_set_layoutcommit relies on the lseg refcount to keep the layout around. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt to reference a null layout.

• 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…

• fix: dm: fix dm_blk_report_zones {CVE-2025-38141}
• ice: Fix a null pointer dereference in ice_copy_and_init_pkg() {CVE-2025-38664}
• qed: Don't collect too many protection override GRC elements {CVE-2025-39949}
• drm/amd/display: Avoid a NULL pointer dereference {CVE-2025-39693}
• iommu/amd/pgtbl: Fix possible race while increase page table level {CVE-2025-39961}
• pNFS: Fix uninited ptr deref in block/scsi layout {CVE-2025-38691}
• netfilter: nf_reject: don't leak dst refcount for loopback packets {CVE-2025-38732}
• net/mlx5: Check device memory pointer before usage {CVE-2025-38645}
• ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() {CVE-2025-71085}
• ice: fix Tx scheduler error handling in XDP callback {CVE-2025-38127}
• tracing: Limit access to parser->buffer when trace_get_user failed {CVE-2025-39683}
• rcu: Protect ->defer_qs_iw_pending from data race {CVE-2025-39749}
• netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX {CVE-2025-38201}
• KVM: x86: use array_index_nospec with indices that come from guest {CVE-2025-39823}
• phy: tegra: xusb: Fix unbalanced regulator disable in UTMI PHY mode {CVE-2025-38535}
• nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec {CVE-2026-22998}
• HID: asus: fix UAF via HID_CLAIMED_INPUT validation {CVE-2025-39824}
• svcrdma: use rc_pageoff for memcpy byte offset {CVE-2025-68811}
• fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds {CVE-2025-40304}
• NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid {CVE-2025-68349}
• cnic: Fix use-after-free bugs in cnic_delete_task {CVE-2025-39945}
• scsi: smartpqi: Fix smp_processor_id() call trace for preemptible kernels {CVE-2025-38288}
• fs: writeback: fix use-after-free in __mark_inode_dirty() {CVE-2025-39866}
• tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork. {CVE-2025-39913}
• net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit {CVE-2025-39766}
• ftrace: Also allocate and copy hash for reading of filter files {CVE-2025-39689}
• fbdev: Fix vmalloc out-of-bounds write in fast_imageblit {CVE-2025-38685}
• HID: core: do not bypass hid_hw_raw_request {CVE-2025-38494}

• smb3: fix for slab out of bounds on mount to ksmbd {CVE-2025-38728}
• netfilter: nft_set_pipapo: clamp maximum map bucket size to INT_MAX {CVE-2025-38201}
• ALSA: usb-audio: Validate UAC3 power domain descriptors, too {CVE-2025-38729}
• net: atm: fix /proc/net/atm/lec handling {CVE-2025-38180}
• tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork. {CVE-2025-39913}
• fs: writeback: fix use-after-free in __mark_inode_dirty() {CVE-2025-39866}
• KVM: SVM: Get source vCPUs from source VM for SEV-ES intrahost migration {CVE-2023-54296}
• 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}
• net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() {CVE-2023-54114}
• isofs: Prevent the use of too small fid {CVE-2025-37780}
• media: dvb-frontends: avoid stack overflow warnings with clang {CVE-2024-27075}
• ipv6: Fix infinite recursion in fib6_dump_done(). {CVE-2024-35886}
• HID: core: do not bypass hid_hw_raw_request {CVE-2025-38494}
• fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds {CVE-2025-40304}
• HID: asus: fix UAF via HID_CLAIMED_INPUT validation {CVE-2025-39824}
• cnic: Fix use-after-free bugs in cnic_delete_task {CVE-2025-39945}
• 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}
• 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}
• 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}
• fbdev: bitblit: bound-check glyph index in bit_putcs* {CVE-2025-40322}
• usb: core: config: Prevent OOB read in SS endpoint companion parsing {CVE-2025-39760}
• mptcp: fix race condition in mptcp_schedule_work() {CVE-2025-40258}
• KVM: x86: Reset IRTE to host control if new route isn't postable {CVE-2025-37885}

• fix: fbdev: fix potential buffer overflow in do_register_framebuffer()
• qed: Don't collect too many protection override GRC elements {CVE-2025-39949}
• drm/amd/display: Avoid a NULL pointer dereference {CVE-2025-39693}
• pNFS: Fix uninited ptr deref in block/scsi layout {CVE-2025-38691}
• netfilter: nf_reject: don't leak dst refcount for loopback packets {CVE-2025-38732}
• ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() {CVE-2025-71085}
• fs: dlm: fix use after free in midcomms commit {CVE-2023-53629}
• svcrdma: use rc_pageoff for memcpy byte offset {CVE-2025-68811}
• bpf: Disable preemption in bpf_perf_event_output {CVE-2023-54303}
• scsi: target: iscsit: Free cmds before session free {CVE-2023-54184}
• fbdev: bitblit: bound-check glyph index in bit_putcs* {CVE-2025-40322}
• scsi: libsas: Fix use-after-free bug in smp_execute_task_sg() {CVE-2022-50422}
• RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem {CVE-2025-38022}
• memcg: protect concurrent access to mem_cgroup_idr {CVE-2024-43892}
• ACPI: EC: Fix oops when removing custom query handlers {CVE-2023-54244}
• KVM: SVM: Get source vCPUs from source VM for SEV-ES intrahost migration {CVE-2023-54296}
• net: nsh: Use correct mac_offset to unwind gso skb in nsh_gso_segment() {CVE-2023-54114}
• net: tls: avoid hanging tasks on the tx_lock {CVE-2023-54306}
• usb: typec: bus: verify partner exists in typec_altmode_attention {CVE-2023-54299}
• scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization {CVE-2023-54234}
• rxrpc: Fix timeout of a call that hasn't yet been granted a channel {CVE-2023-54195}
• block, bfq: Fix division by zero error on zero wsum {CVE-2023-54242}
• wifi: cfg80211: reject auth/assoc to AP with our address {CVE-2023-53540}
• wifi: iwlwifi: mvm: don't trust firmware n_channels {CVE-2023-53589}
• wifi: mac80211: check for station first in client probe {CVE-2023-53588}
• bonding: do not assume skb mac_header is set {CVE-2023-53601}
• drm/i915: Make intel_get_crtc_new_encoder() less oopsy {CVE-2023-53571}
• wifi: rtw88: delete timer and free skb queue when unloading {CVE-2023-53574}
• net: bcmgenet: Add a check for oversized packets {CVE-2023-53535}
• media: uvcvideo: Fix memory leak in uvc_gpio_parse {CVE-2022-50882}
• md/raid10: fix memleak of md thread {CVE-2023-54294}
• usb: typec: altmodes/displayport: fix pin_assignment_show {CVE-2023-54186}
• scsi: qedf: Fix NULL dereference in error handling {CVE-2023-54289}
• HID: multitouch: Add NULL check in mt_input_configured {CVE-2024-58020}
• driver core: fix potential null-ptr-deref in device_add() {CVE-2023-54321}
• net: usb: smsc75xx: Move packet length check to prevent kernel panic in skb_pull {CVE-2023-53125}
• rcuscale: Move rcu_scale_writer() schedule_timeout_uninterruptible() to _idle() {CVE-2023-54246}
• bpf: Address KCSAN report on bpf_lru_list {CVE-2023-54283}
• usb: core: config: Prevent OOB read in SS endpoint companion parsing {CVE-2025-39760}
• nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec {CVE-2026-22998}
• drm/i915: fix race condition UAF in i915_perf_add_config_ioctl {CVE-2023-54202}
• mmc: via-sdmmc: fix return value check of mmc_add_host() {CVE-2022-50846}
• bpf: Disable preemption in bpf_event_output {CVE-2023-54173}
• net/mlx5e: Move representor neigh cleanup to profile cleanup_tx {CVE-2023-54148}
• net/mlx5: Handle pairing of E-switch via uplink un/load APIs {CVE-2023-53347}
• net/mlx5e: Fix cleanup null-ptr deref on encap lock {CVE-2023-53105}
• smb3: fix for slab out of bounds on mount to ksmbd {CVE-2025-38728}
• perf/core: Exit early on perf_mmap() fail {CVE-2025-38565}
• HID: core: do not bypass hid_hw_raw_request {CVE-2025-38494}
• HID: core: ensure __hid_request reserves the report ID as the first byte
• HID: core: ensure the allocated report buffer can contain the reserved report ID {CVE-2025-38495}
• HID: intel-ish-hid: Fix kernel panic during warm reset {CVE-2023-53392}
• xfs: do not propagate ENODATA…

• CVE-2025-39683
  • tracing: Remove unneeded goto out logic {CVE-2025-39683}
  • tracing: Limit access to parser->buffer when trace_get_user failed {CVE-2025-39683}
• CVE-2025-38079
  • crypto: algif_hash - fix double free in hash_accept {CVE-2025-38079}
• CVE-2025-38159
  • wifi: rtw88: fix the 'para' buffer size to avoid reading out of bounds {CVE-2025-38159}
• CVE-2025-38211
  • RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction {CVE-2025-38211}
• CVE-2025-38024
  • RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug {CVE-2025-38024}
• CVE-2025-38103
  • HID: hyperv: Correctly access fields declared as __le16 {CVE-2025-38103}
  • HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse() {CVE-2025-38103}
• CVE-2025-38157
  • wifi: ath9k_htc: Abort software beacon handling if disabled {CVE-2025-38157}
• CVE-2025-38230
  • jfs: add sanity check for agwidth in dbMount {CVE-2025-38230}
  • fs/jfs: consolidate sanity checking in dbMount {CVE-2025-38230}
  • jfs: validate AG parameters in dbMount() to prevent crashes {CVE-2025-38230}
• CVE-2025-39955
  • tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). {CVE-2025-39955}
• CVE-2025-38680
  • media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() {CVE-2025-38680}
• CVE-2025-38708
  • drbd: add missing kref_get in handle_write_conflicts {CVE-2025-38708}
• CVE-2025-39759
  • btrfs: qgroup: introduce quota mode {CVE-2025-39759}
  • btrfs: qgroup: fix race between quota disable and quota rescan ioctl {CVE-2025-39759}
• CVE-2025-38666
  • net: appletalk: Fix use-after-free in AARP proxy probe {CVE-2025-38666}
• CVE-2025-40269
  • ALSA: usb-audio: Improve frames size computation {CVE-2025-40269}
  • ALSA: usb-audio: Replace s/frame/packet/ where appropriate {CVE-2025-40269}
  • ALSA: usb-audio: Fix potential overflow of PCM transfer buffer {CVE-2025-40269}
• CVE-2025-40149
  • net: netdevice: Add operation ndo_sk_get_lower_dev {CVE-2025-40149}
  • net/tls: Device offload to use lowest netdevice in chain {CVE-2025-40149}
  • tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock(). {CVE-2025-40149}
• CVE-2025-71089
  • iommu: disable SVA when CONFIG_X86 is set {CVE-2025-71089}
• CVE-2026-23234
  • f2fs: fix to avoid UAF in f2fs_write_end_io() {CVE-2026-23234}
• CVE-2026-23089
  • ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() {CVE-2026-23089}
• CVE-2026-23074
  • net/sched: Enforce that teql can only be used as root qdisc {CVE-2026-23074}
• CVE-2026-23061
  • can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak {CVE-2026-23061}
• CVE-2026-23060
  • crypto: authencesn - reject too-short AAD (assoclen<8) to match ESP/ESN spec {CVE-2026-23060}
• CVE-2026-22997
  • net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts {CVE-2026-22997}
• CVE-2026-22991
  • libceph: make free_choose_arg_map() resilient to partial allocation {CVE-2026-22991}
• CVE-2026-22990
  • libceph: replace overzealous BUG_ON in osdmap_apply_incremental() {CVE-2026-22990}
• CVE-2026-22978
  • wifi: avoid kernel-infoleak from struct iw_point {CVE-2026-22978}
• CVE-2026-22977
  • net: sock: fix hardened usercopy panic in sock_recv_errqueue {CVE-2026-22977}
• CVE-2025-71154
  • net: usb: rtl8150: fix memory leak on usb_submit_urb() failure {CVE-2025-71154}
• CVE-2025-71085
  • ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() {CVE-2025-71085}
• CVE-2025-68734
  • isdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe() {CVE-2025-68734}
• CVE-2025-68349
  • NFSv4/pNFS: Clear…

• ovl: Filter invalid inodes with missing lookup function {CVE-2024-56570}
• ALSA: aloop: Fix racy access at PCM trigger {CVE-2026-23191}
• media: imon: reorganize serialization {CVE-2025-39993}
• usb: xhci: Fix inverted ring_xrun_event check in handle_tx_event() {CVE-2025-37882}
• Revert "VFS: Impose ordering on accesses of d_inode and d_flags"
• Revert "VFS: Combine inode checks with d_is_negative() and d_is_positive() in pathwalk"
• Revert "namei: d_is_negative() should be checked before ->d_seq validation"
• Revert "namei: results of d_is_negative() should be checked after dentry revalidation"
• Revert "namei: ->d_inode of a pinned dentry is stable only for positives"
• scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() {CVE-2026-23193}
• net/sched: cls_u32: use skb_header_pointer_careful() {CVE-2026-23204}
• net: add skb_header_pointer_careful() helper {CVE-2026-23204}
• ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() {CVE-2026-23089}
• NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid {CVE-2025-68349}
• net/sched: Enforce that teql can only be used as root qdisc {CVE-2026-23074}

• 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

• ovl: Filter invalid inodes with missing lookup function {CVE-2024-56570}
• ALSA: aloop: Fix racy access at PCM trigger {CVE-2026-23191}
• media: imon: reorganize serialization {CVE-2025-39993}
• usb: xhci: Fix inverted ring_xrun_event check in handle_tx_event() {CVE-2025-37882}
• Revert "VFS: Impose ordering on accesses of d_inode and d_flags"
• Revert "VFS: Combine inode checks with d_is_negative() and d_is_positive() in pathwalk"
• Revert "namei: d_is_negative() should be checked before ->d_seq validation"
• Revert "namei: results of d_is_negative() should be checked after dentry revalidation"
• Revert "namei: ->d_inode of a pinned dentry is stable only for positives"
• scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() {CVE-2026-23193}
• net/sched: cls_u32: use skb_header_pointer_careful() {CVE-2026-23204}
• net: add skb_header_pointer_careful() helper {CVE-2026-23204}
• ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() {CVE-2026-23089}
• NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid {CVE-2025-68349}
• net/sched: Enforce that teql can only be used as root qdisc {CVE-2026-23074}

• ovl: Filter invalid inodes with missing lookup function {CVE-2024-56570}
• ALSA: aloop: Fix racy access at PCM trigger {CVE-2026-23191}
• media: imon: reorganize serialization {CVE-2025-39993}
• usb: xhci: Fix inverted ring_xrun_event check in handle_tx_event() {CVE-2025-37882}
• Revert "VFS: Impose ordering on accesses of d_inode and d_flags"
• Revert "VFS: Combine inode checks with d_is_negative() and d_is_positive() in pathwalk"
• Revert "namei: d_is_negative() should be checked before ->d_seq validation"
• Revert "namei: results of d_is_negative() should be checked after dentry revalidation"
• Revert "namei: ->d_inode of a pinned dentry is stable only for positives"
• scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() {CVE-2026-23193}
• net/sched: cls_u32: use skb_header_pointer_careful() {CVE-2026-23204}
• net: add skb_header_pointer_careful() helper {CVE-2026-23204}
• ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() {CVE-2026-23089}
• NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid {CVE-2025-68349}
• net/sched: Enforce that teql can only be used as root qdisc {CVE-2026-23074}