In the Linux kernel, the following vulnerability has been resolved:
ksmbd: vfs: fix race on mflags in vfscache
ksmbd maintains delete-on-close and pending-delete state in ksmbdinode->mflags. In vfscache.c this field is accessed under inconsistent locking: some paths read and modify mflags under ci->m_lock while others do so without taking the lock at all.
Examples:
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:
This unifies the locking around m_flags and removes the data race while preserving the existing delete-on-close behaviour.
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68809.json",
"cna_assigner": "Linux"
}