The vulnerability in the Linux kernel's ksmbd subsystem involves a race condition on the m_flags field of ksmbd_inode, which tracks delete-on-close and pending-delete states. Different code paths accessed m_flags with inconsistent locking, causing potential data races when multiple threads concurrently open, close, or delete the same file. This could result in files either not being deleted when expected or being deleted prematurely. The fix applies consistent locking (ci->m_lock) around all accesses to m_flags, ensuring atomicity and preventing race conditions without altering the delete-on-close behavior.

The vulnerability can cause inconsistent file deletion behavior in ksmbd shares, such as files remaining on disk after a delete-on-close operation or files disappearing while still in use. This impacts data integrity and availability on affected systems using ksmbd for SMB file sharing. There is no confidentiality impact. The CVSS vector indicates no confidentiality impact but high integrity and availability impact.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description states it has been resolved in the Linux kernel, implying an official fix exists. Users should apply the relevant Linux kernel updates that include this fix once available. Until then, no specific workaround is described.