CVE-2025-68809 Details
Description
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.
A race condition vulnerability has been identified in the Linux kernel's ksmbd component, specifically within the virtual file system (VFS) cache management. This vulnerability arises from inconsistent locking mechanisms when accessing the delete-on-close and pending-delete states maintained in the ksmbd_inode structure. Some functions properly use the ci->m_lock to synchronize access to the m_flags field, while others do not, leading to potential data races. This issue can occur when multiple threads concurrently open, close, and delete the same file, causing the delete-on-close and pending-delete indicators to be lost or misrepresented. As a result, files may remain on disk after being marked for deletion or disappear unexpectedly while still in use.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been addressed. Instructions for downloading the patched version are available on the Linux Kernel Archive.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Jan 13, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/5adad9727a815c26013b0d41cfee92ffa7d4037c | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/991f8a79db99b14c48d20d2052c82d65b9186cad | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/a4fd1fdf505facfae26b5654c9eff321f4cbc1a7 | kernel.org | |
| https://git.kernel.org/stable/c/ccc78781041589ea383e61d5d7a1e9a31b210b93 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/ee63729760f5b61a66f345c54dc4c7514e62383d | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
| ksmbd | All versions |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 30, 2026 | CVE Modified | kernel.org |
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jan 13, 2026 | New CVE Received | kernel.org |
Volerion