CVE-2025-21731

The Linux kernel contains a use-after-free (UAF) vulnerability in the nbd driver. The flaw exists because the driver allows reconnection after a disconnect, leading to a race condition where nbd_config memory is freed while still referenced. Specifically, if a reference is grabbed and then nbd_ge...

CVE-2025-21727

CVE-2025-21727 : Linux kernel issue in padata_reorder causing a use-after-free in padata_find_next under certain race conditions. The provided connected documents confirm a KASAN UAF scenario when a parallel padata_reorder/serial flow frees Pd too early and later calls padata_find_next. The remed...

CVE-2025-21727

In the Linux kernel, the following vulnerability has been resolved: padata: fix UAF in padatareorder A bug was found when run ltp test: BUG: KASAN: slab-use-after-free in padatafindnext+0x29/0x1a0 Read of size 4 at addr ffff88bbfe003524 by task kworker/u113:2/3039206 CPU: 0 PID: 3039206 Comm:...

CVE-2025-21726

In the Linux kernel, the following vulnerability has been resolved: padata: avoid UAF for reorderwork Although the previous patch can avoid ps and ps UAF for doserial, it can not avoid potential UAF issue for reorderwork. This issue can happen just as below: cryptorequest cryptorequest cryptodela...

CVE-2025-21725

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix oops due to unset link speed It isn't guaranteed that NETWORKINTERFACEINFO::LinkSpeed will always be set by the server, so the client must handle any values and then prevent oopses like below from happening: Oops...

CVE-2025-21725 smb: client: fix oops due to unset link speed

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix oops due to unset link speed It isn't guaranteed that NETWORKINTERFACEINFO::LinkSpeed will always be set by the server, so the client must handle any values and then prevent oopses like below from happening: Oops...

CVE-2025-21726

In CVE-2025-21726, the Linux kernel padata subsystem had a use-after-free (UAF) in the reorder_work path. The root cause was that the previous patch did not hold a reference to 'pd' long enough when queuing reorder_work. The fix is to take a reference to 'pd' before queuing reorder_work and to ke...

CVE-2025-21724

In the Linux kernel, the following vulnerability has been resolved: iommufd/iovabitmap: Fix shift-out-of-bounds in iovabitmapoffsettoindex Resolve a UBSAN shift-out-of-bounds issue in iovabitmapoffsettoindex where shifting the constant "1" of type int by bitmap-mapped.pgshift an unsigned long val...

CVE-2025-21722 nilfs2: do not force clear folio if buffer is referenced

In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not force clear folio if buffer is referenced Patch series "nilfs2: protect busy buffer heads from being force-cleared". This series fixes the buffer head state inconsistency issues reported by syzbot that occurs when...

CVE-2025-21723

Summary (CVE-2025-21723) In the Linux kernel, mpi3mr/scsi code was fixed to prevent a crash when BSG setup fails. If bsg_setup_queue() fails, bsg_queue may be non-NULL, causing mpi3mr_bsg_exit() to skip bsg_remove_queue() and trigger a NULL pointer dereference (kernel crash) as shown in the entry...

CVE-2025-21723 scsi: mpi3mr: Fix possible crash when setting up bsg fails

In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix possible crash when setting up bsg fails If bsgsetupqueue fails, the bsgqueue is assigned a non-NULL value. Consequently, in mpi3mrbsgexit, the condition "if!mrioc-bsgqueue" will not be satisfied, preventing...

CVE-2025-21720 xfrm: delete intermediate secpath entry in packet offload mode

In the Linux kernel, the following vulnerability has been resolved: xfrm: delete intermediate secpath entry in packet offload mode Packets handled by hardware have added secpath as a way to inform XFRM core code that this path was already handled. That secpath is not needed at all after policy is...

CVE-2025-21719

In the Linux kernel, the following vulnerability has been resolved: ipmr: do not call mrmfcusesdev for unres entries syzbot found that calling mrmfcusesdev for unres entries would crash 1, because c-mfcun.res.minvif / c-mfcun.res.maxvif alias to "struct skbuffhead unresolved", which contain two...

CVE-2025-21717

CVE-2025-21717 affects the Linux kernel mlx5e path: kvzalloc_node lacks cpu_to_node conversion, allowing an out-of-bounds access when ethtool/netlink calls mlx5e_open on a CPU above MAX_NUMNODES, potentially panicking the kernel. The issue is fixed by adding a missing cpu_to_node conversion to ml...

CVE-2025-21716

In the Linux kernel, the following vulnerability has been resolved: vxlan: Fix uninit-value in vxlanvnifilterdump KMSAN reported an uninit-value access in vxlanvnifilterdump 1. If the length of the netlink message payload is less than sizeofstruct tunnelmsg, vxlanvnifilterdump accesses bytes beyo...

CVE-2025-21715 net: davicom: fix UAF in dm9000_drv_remove

In the Linux kernel, the following vulnerability has been resolved: net: davicom: fix UAF in dm9000drvremove dm is netdev private data and it cannot be used after freenetdev call. Using dm after freenetdev can cause UAF bug. Fix it by moving freenetdev at the end of the function. This is similar ...

CVE-2025-21713

CVE-2025-21713 affects the PowerPC/ pSeries IOMMU path in the Linux kernel. The issue occurs when reusing the same vfio container across different IOMMU groups, where spapr_tce_set_window() may lead to cleanup that dereferences a null or invalid tbl, causing a kernel crash (NULL pointer dereferen...

CVE-2025-21713 powerpc/pseries/iommu: Don't unset window if it was never set

In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries/iommu: Don't unset window if it was never set On pSeries, when user attempts to use the same vfio container used by different iommu group, the spaprtcesetwindow returns -EPERM and the subsequent cleanup leads to t...

CVE-2025-21712

In the Linux kernel, the md/md-bitmap component had a race where bitmap_get_stats() could be called while the bitmap storage was destroyed or not fully initialized, risking a general protection fault. The root cause was dereferencing bitmap->storage outside a synchronized lifetime of the bitma...

CVE-2025-21709 kernel: be more careful about dup_mmap() failures and uprobe registering

In the Linux kernel, the following vulnerability has been resolved: kernel: be more careful about dupmmap failures and uprobe registering If a memory allocation fails during dupmmap, the maple tree can be left in an unsafe state for other iterators besides the exit path. All the locks are dropped...