{
  "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:  nvmet: fix max_qid race between configfs and controller allocation  The function nvmet_subsys_attr_qid_max_store() can race against nvmet_alloc_ctrl() when a subsystem's max_qid limit is modified.  Suppose max_qid is currently 64. If nvmet_alloc_ctrl() executes: ctrl-\u003esqs = kzalloc_objs(struct nvmet_sq *, subsys-\u003emax_qid + 1); and at this exact point, a userspace process changes max_qid to 128, nvmet_subsys_attr_qid_max_store() will set the new max_qid value. It attempts to delete active controllers to force a reconnect, but the new controller won't be deleted because it hasn't been added to the subsys-\u003ectrls list yet.  nvmet_alloc_ctrl() then proceeds and adds the new controller to the subsys-\u003ectrls list. Later, when nvmet_install_queue() is called, it will see max_qid set to 128, but the memory allocated for sqs is only sized for 64 entries. This results in a KASAN out-of-bounds warning and potential memory corruptions.  Fix this by protecting the queue allocations and list insertion in nvmet_alloc_ctrl() with down_read(\u0026nvmet_config_sem). Because nvmet_subsys_attr_qid_max_store() acquires down_write(\u0026nvmet_config_sem) to modify the attribute, this safely prevents the configfs writer from modifying max_qid during controller creation.  Copy the max_qid from the subsystem to the controller's structure during the allocation; ctrl-\u003emax_qid never changes as long as the controller remains in LIVE state, so this will prevent similar race conditions.",
  "id": "DEBIAN-CVE-2026-90206",
  "modified": "2026-09-18T04:47:27.226872309Z",
  "published": "2026-09-17T17:17:15.700Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-90206"
    }
  ],
  "upstream": [
    "CVE-2026-90206"
  ]
}