{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.85-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.0.3-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fix use-after-free in __ksmbd_close_fd() via durable scavenger  When a durable file handle survives session disconnect (TCP close without SMB2_LOGOFF), session_fd_check() sets fp-\u003econn = NULL to preserve the handle for later reconnection. However, it did not clean up the byte-range locks on fp-\u003elock_list.  Later, when the durable scavenger thread times out and calls __ksmbd_close_fd(NULL, fp), the lock cleanup loop did:      spin_lock(\u0026fp-\u003econn-\u003ellist_lock);  This caused a slab use-after-free because fp-\u003econn was NULL and the original connection object had already been freed by ksmbd_tcp_disconnect().  The root cause is asymmetric cleanup: lock entries (smb_lock-\u003eclist) were left dangling on the freed conn-\u003elock_list while fp-\u003econn was nulled out.  To fix this issue properly, we need to handle the lifetime of smb_lock-\u003eclist across three paths:  - Safely skip clist deletion when list is empty and fp-\u003econn is NULL.  - Remove the lock from the old connection's lock_list in    session_fd_check()  - Re-add the lock to the new connection's lock_list in    ksmbd_reopen_durable_fd().",
  "id": "DEBIAN-CVE-2026-31718",
  "modified": "2026-09-14T16:47:46.900132378Z",
  "published": "2026-05-01T14:16:21.963Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-31718"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-31718"
  ]
}