{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.3.3-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fix app-instance non-durable supersede session UAF  ksmbd_close_fd_app_instance_id() supersedes a prior open that has the same AppInstanceId. It reaches that open's session through opinfo-\u003esess. This pointer is not refcounted.  Session teardown detaches durable handles before it frees the session. It does not detach a non-durable open. That open still points at the session through opinfo-\u003esess after the session is freed. Another session can supersede the open at the same time. The supersede then takes a write lock through the stale pointer, in the freed session's file table.    BUG: KASAN: slab-use-after-free in _raw_write_lock+0x71/0xd0   Call Trace:    _raw_write_lock+0x71/0xd0    ksmbd_close_fd_app_instance_id+0xd9/0x670 [ksmbd]    smb2_open+0x3e10/0xd910 [ksmbd]   Freed by task 212:    ksmbd_session_destroy+0x38d/0x480 [ksmbd]  Fix this by looking the session up by opinfo-\u003esession_id. The lookup returns a reference, as smb2_break_collect_channels() does. Recheck that opinfo-\u003esess still points at it before using it.  Do the lookup without m_lock held. destroy_previous_session() takes m_lock under the session table lock, and taking them in the other order here would deadlock.",
  "id": "DEBIAN-CVE-2026-99289",
  "modified": "2026-11-17T04:47:45.884617322Z",
  "published": "2026-11-16T10:17:00.870Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-99289"
    }
  ],
  "upstream": [
    "CVE-2026-99289"
  ]
}