{
  "cveId": "CVE-2025-68809",
  "url": "https://patchblox.com/security/cve/CVE-2025-68809",
  "summary": "CVE-2025-68809 is fixed in linux on 1 platform, first by DEBIAN-CVE-2025-68809, released January 13, 2026. It is not reported as exploited. Patch Radar priority: High.",
  "title": "ksmbd: vfs: fix race on m_flags in vfs_cache",
  "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-\u003Em_flags. In vfs_cache.c this field is accessed under inconsistent locking: some paths read and modify m_flags under ci-\u003Em_lock while others do so without taking the lock at all.  Examples:   - ksmbd_query_inode_status() and __ksmbd_inode_close() use    ci-\u003Em_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-\u003Em_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-\u003Em_lock    after dropping inode_hash_lock.  - Adding ci-\u003Em_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-\u003Em_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.",
  "published": "2026-01-13T16:16:03Z",
  "severity": "Moderate",
  "cvss": 9.1,
  "cvssVector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H",
  "epss": 0.00528,
  "epssPercentile": 0.44923,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "vendorAdvisory": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-68809",
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.12.69-1",
      "fix": "DEBIAN-CVE-2025-68809",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2025-68809",
      "released": "2026-01-13T16:16:03Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.18.3-1",
      "fix": "DEBIAN-CVE-2025-68809",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2025-68809",
      "released": "2026-01-13T16:16:03Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T00:53:09Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}