cbcvebase.
CVE-2026-64142
published 2026-07-19

CVE-2026-64142: In the Linux kernel, the following vulnerability has been resolved: ksmbd: close durable scavenger races against m_fp_list lookups ksmbd_durable_scavenger()…

PriorityP352critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.70%
53.1th percentile
In the Linux kernel, the following vulnerability has been resolved: ksmbd: close durable scavenger races against m_fp_list lookups ksmbd_durable_scavenger() has two related races against any walker that iterates f_ci->m_fp_list, including ksmbd_lookup_fd_inode() (used by ksmbd_vfs_rename) and the share-mode checks in fs/smb/server/smb_common.c. (1) fp->node list-head reuse. Durable-preserved handles can remain linked on f_ci->m_fp_list after session teardown so share-mode checks still see them while the handle is reconnectable. The scavenger collected expired handles by adding fp->node to a local scavenger_list after removing them from the global durable idr. Because fp->node is the same list_head used by m_fp_list, list_add(&fp->node, &scavenger_list) overwrites the m_fp_list links and corrupts both lists. CONFIG_DEBUG_LIST can report this on the share-mode walk path. (2) Refcount race against m_fp_list walkers. The scavenger qualifies an expired durable handle with atomic_read(&fp->refcount) > 1 and fp->conn under global_ft.lock, removes fp from global_ft, then drops global_ft.lock before unlinking fp from m_fp_list and freeing it. During that gap fp is still linked on m_fp_list with f_state == FP_INITED. ksmbd_lookup_fd_inode() under m_lock read calls ksmbd_fp_get() (atomic_inc_not_zero on refcount that is still 1) and takes a live reference; the scavenger then unlinks and frees fp while the holder owns a reference, leading to UAF on the holder's subsequent ksmbd_fd_put() and on any field reads performed by a concurrent share-mode walker that iterates m_fp_list without taking ksmbd_fp_get() (smb_check_perm_dleases-like paths). Fix both: * Stop reusing fp->node as a scavenger-private list node. Remove one expired handle from global_ft under global_ft.lock, take an explicit transient reference, drop the lock, unlink fp->node from m_fp_list under f_ci->m_lock, then drop both the durable lifetime and transient references with atomic_sub_and_test(2, &fp->refcoun

Affected

23 ranges
VendorProductVersion rangeFixed in
linuxlinux——
linuxlinux>= 7f0cb478703cbeaddfe5c9101c5c73cd975d1073 < 3a436932eb397e909d0607d76a8325abd9d85a353a436932eb397e909d0607d76a8325abd9d85a35
linuxlinux>= d484d621d40f4a8b8959008802d79bef3609641b < 95f072ef934ca00711d510676b8792cbf59a5aae95f072ef934ca00711d510676b8792cbf59a5aae
linuxlinux>= d484d621d40f4a8b8959008802d79bef3609641b < 5da69a65b282d2276de22e5194ba0f88c836170c5da69a65b282d2276de22e5194ba0f88c836170c
linuxlinux>= d484d621d40f4a8b8959008802d79bef3609641b < 1f8f3246d55f89350a1a67bdf3744b7241048e4e1f8f3246d55f89350a1a67bdf3744b7241048e4e
linuxlinux>= d484d621d40f4a8b8959008802d79bef3609641b < bf736184d063da1a552ffeff0481813599a182ccbf736184d063da1a552ffeff0481813599a182cc
linuxlinux_kernel——
linuxlinux_kernel——
linuxlinux_kernel>= 6.11 < 6.12.926.12.92
linuxlinux_kernel>= 6.13 < 6.18.346.18.34
linuxlinux_kernel>= 6.19 < 7.0.117.0.11
ubuntulinux-aws——
ubuntulinux-azure——
ubuntulinux-azure-7.0——
ubuntulinux-azure-fde——
ubuntulinux-gcp-7.0——
ubuntulinux-ibm——
ubuntulinux-nvidia——
ubuntulinux-nvidia-7.0——
ubuntulinux-nvidia-bos——
ubuntulinux-oracle——
ubuntulinux-oracle-7.0——
ubuntulinux-raspi——

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vendor_redhat9.8CRITICAL
vendor_ubuntu9.1CRITICAL
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.