{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: defer publishing granted locks to prevent UAF/double-free race  In smb2_lock(), mid-batch granted locks are published to connection-wide (conn-\u003elock_list) and file-wide (fp-\u003elock_list) lists immediately upon vfs_lock_file() success, while also remaining tracked on the stack-local rollback_list.  If a subsequent element in the same SMB2_LOCK request array fails validation or execution, the thread jumps to out: and walks rollback_list to undo previously granted locks. However, because the granted lock was already published to conn-\u003elock_list, a concurrent UNLOCK request on the same connection can find the lock object and kfree() it before the rollback loop executes.  When the granting thread subsequently walks rollback_list, it dereferences and frees the already-freed ksmbd_lock structure, resulting in a Use-After-Free and Double-Free (on both ksmbd_lock and struct file_lock).  Fix this by deferring the publication of granted locks to conn-\u003elock_list and fp-\u003elock_list until after the entire array of lock elements has been processed without error. Mid-batch grants remain tracked exclusively on the request-local rollback_list until the whole batch succeeds, eliminating the race window.",
  "id": "DEBIAN-CVE-2026-90162",
  "modified": "2026-09-18T04:47:36.400438402Z",
  "published": "2026-09-17T17:17:09.517Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-90162"
    }
  ],
  "upstream": [
    "CVE-2026-90162"
  ]
}