{
  "threat_severity" : "Moderate",
  "public_date" : "2026-01-13T00:00:00Z",
  "bugzilla" : {
    "description" : "kernel: ksmbd: vfs: fix race on m_flags in vfs_cache",
    "id" : "2429056",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2429056"
  },
  "details" : [ "In the Linux kernel, the following vulnerability has been resolved:\nksmbd: vfs: fix race on m_flags in vfs_cache\nksmbd maintains delete-on-close and pending-delete state in\nksmbd_inode->m_flags. In vfs_cache.c this field is accessed under\ninconsistent locking: some paths read and modify m_flags under\nci->m_lock while others do so without taking the lock at all.\nExamples:\n- ksmbd_query_inode_status() and __ksmbd_inode_close() use\nci->m_lock when checking or updating m_flags.\n- ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(),\nksmbd_clear_inode_pending_delete() and ksmbd_fd_set_delete_on_close()\nused to read and modify m_flags without ci->m_lock.\nThis creates a potential data race on m_flags when multiple threads\nopen, close and delete the same file concurrently. In the worst case\ndelete-on-close and pending-delete bits can be lost or observed in an\ninconsistent state, leading to confusing delete semantics (files that\nstay on disk after delete-on-close, or files that disappear while still\nin use).\nFix it by:\n- Making ksmbd_query_inode_status() look at m_flags under ci->m_lock\nafter dropping inode_hash_lock.\n- Adding ci->m_lock protection to all helpers that read or modify\nm_flags (ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(),\nksmbd_clear_inode_pending_delete(), ksmbd_fd_set_delete_on_close()).\n- Keeping the existing ci->m_lock protection in __ksmbd_inode_close(),\nand moving the actual unlink/xattr removal outside the lock.\nThis unifies the locking around m_flags and removes the data race while\npreserving the existing delete-on-close behaviour." ],
  "package_state" : [ {
    "product_name" : "Red Hat Enterprise Linux 10",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:10"
  }, {
    "product_name" : "Red Hat Enterprise Linux 6",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:6"
  }, {
    "product_name" : "Red Hat Enterprise Linux 7",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:7"
  }, {
    "product_name" : "Red Hat Enterprise Linux 7",
    "fix_state" : "Not affected",
    "package_name" : "kernel-rt",
    "cpe" : "cpe:/o:redhat:enterprise_linux:7"
  }, {
    "product_name" : "Red Hat Enterprise Linux 8",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:8"
  }, {
    "product_name" : "Red Hat Enterprise Linux 8",
    "fix_state" : "Not affected",
    "package_name" : "kernel-rt",
    "cpe" : "cpe:/o:redhat:enterprise_linux:8"
  }, {
    "product_name" : "Red Hat Enterprise Linux 9",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:9"
  }, {
    "product_name" : "Red Hat Enterprise Linux 9",
    "fix_state" : "Not affected",
    "package_name" : "kernel-rt",
    "cpe" : "cpe:/o:redhat:enterprise_linux:9"
  } ],
  "references" : [ "https://www.cve.org/CVERecord?id=CVE-2025-68809\nhttps://nvd.nist.gov/vuln/detail/CVE-2025-68809\nhttps://lore.kernel.org/linux-cve-announce/2026011311-CVE-2025-68809-e875@gregkh/T" ],
  "name" : "CVE-2025-68809",
  "csaw" : false
}