cbcvebase.
CVE-2025-68809
published 2026-01-13

CVE-2025-68809: In the Linux kernel, the following vulnerability has been resolved: ksmbd: vfs: fix race on m_flags in vfs_cache ksmbd maintains delete-on-close and…

PriorityP349critical9.1CVSS 3.1
AVNACLPRNUINSUCNIHAH
EPSS
0.44%
36.2th percentile
In the Linux kernel, the following vulnerability has been resolved: ksmbd: vfs: fix race on m_flags in vfs_cache ksmbd maintains delete-on-close and pending-delete state in ksmbd_inode->m_flags. In vfs_cache.c this field is accessed under inconsistent locking: some paths read and modify m_flags under ci->m_lock while others do so without taking the lock at all. Examples: - ksmbd_query_inode_status() and __ksmbd_inode_close() use ci->m_lock when checking or updating m_flags. - ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(), ksmbd_clear_inode_pending_delete() and ksmbd_fd_set_delete_on_close() used to read and modify m_flags without ci->m_lock. This creates a potential data race on m_flags when multiple threads open, close and delete the same file concurrently. In the worst case delete-on-close and pending-delete bits can be lost or observed in an inconsistent state, leading to confusing delete semantics (files that stay on disk after delete-on-close, or files that disappear while still in use). Fix it by: - Making ksmbd_query_inode_status() look at m_flags under ci->m_lock after dropping inode_hash_lock. - Adding ci->m_lock protection to all helpers that read or modify m_flags (ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(), ksmbd_clear_inode_pending_delete(), ksmbd_fd_set_delete_on_close()). - Keeping the existing ci->m_lock protection in __ksmbd_inode_close(), and moving the actual unlink/xattr removal outside the lock. This unifies the locking around m_flags and removes the data race while preserving the existing delete-on-close behaviour.

Affected

40 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.18.3-1 (forky)linux 6.18.3-1 (forky)
linuxlinux
linuxlinux>= f44158485826c076335d6860d35872271a83791d < 5adad9727a815c26013b0d41cfee92ffa7d4037c5adad9727a815c26013b0d41cfee92ffa7d4037c
linuxlinux>= f44158485826c076335d6860d35872271a83791d < ccc78781041589ea383e61d5d7a1e9a31b210b93ccc78781041589ea383e61d5d7a1e9a31b210b93
linuxlinux>= f44158485826c076335d6860d35872271a83791d < ee63729760f5b61a66f345c54dc4c7514e62383dee63729760f5b61a66f345c54dc4c7514e62383d
linuxlinux>= f44158485826c076335d6860d35872271a83791d < 991f8a79db99b14c48d20d2052c82d65b9186cad991f8a79db99b14c48d20d2052c82d65b9186cad
linuxlinux_kernel>= 0 < 6.12.69-16.12.69-1
linuxlinux_kernel>= 0 < 6.18.3-16.18.3-1
linuxlinux_kernel>= 5.15.0 < 6.6.1206.6.120
linuxlinux_kernel>= 6.13.0 < 6.18.36.18.3
linuxlinux_kernel>= 6.7.0 < 6.12.646.12.64
ubuntulinux-aws
ubuntulinux-aws-6.17
ubuntulinux-aws-fips
ubuntulinux-azure
ubuntulinux-azure-6.17
ubuntulinux-azure-6.8
ubuntulinux-azure-fips
ubuntulinux-fips
ubuntulinux-gcp
ubuntulinux-gcp-6.17
ubuntulinux-gcp-6.8
ubuntulinux-gcp-fips
ubuntulinux-hwe-6.17
ubuntulinux-hwe-6.8

CVSS provenance

nvdv3.19.1CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
vendor_ubuntu6.4MEDIUM
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.