{"api_version":"1","generated_at":"2026-09-18T16:41:25+00:00","cve":"CVE-2026-90206","urls":{"html":"https://cve.report/CVE-2026-90206","api":"https://cve.report/api/cve/CVE-2026-90206.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-90206","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-90206"},"summary":{"title":"nvmet: fix max_qid race between configfs and controller allocation","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix max_qid race between configfs and controller allocation\n\nThe function nvmet_subsys_attr_qid_max_store() can race against\nnvmet_alloc_ctrl() when a subsystem's max_qid limit is modified.\n\nSuppose max_qid is currently 64. If nvmet_alloc_ctrl() executes:\nctrl->sqs = kzalloc_objs(struct nvmet_sq *, subsys->max_qid + 1);\nand at this exact point, a userspace process changes max_qid to 128,\nnvmet_subsys_attr_qid_max_store() will set the new max_qid value. It\nattempts to delete active controllers to force a reconnect, but the\nnew controller won't be deleted because it hasn't been added to the\nsubsys->ctrls list yet.\n\nnvmet_alloc_ctrl() then proceeds and adds the new controller to the\nsubsys->ctrls list. Later, when nvmet_install_queue() is called, it\nwill see max_qid set to 128, but the memory allocated for sqs is only\nsized for 64 entries. This results in a KASAN out-of-bounds warning\nand potential memory corruptions.\n\nFix this by protecting the queue allocations and list insertion in\nnvmet_alloc_ctrl() with down_read(&nvmet_config_sem). Because\nnvmet_subsys_attr_qid_max_store() acquires down_write(&nvmet_config_sem)\nto modify the attribute, this safely prevents the configfs writer from\nmodifying max_qid during controller creation.\n\nCopy the max_qid from the subsystem to the controller's structure\nduring the allocation; ctrl->max_qid never changes as long as the\ncontroller remains in LIVE state, so this will prevent similar race\nconditions.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-17 17:17:15","updated_at":"2026-09-17 17:17:15"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/2c23fc91789dfd9db746edb3ae9b90d65fabd410","name":"https://git.kernel.org/stable/c/2c23fc91789dfd9db746edb3ae9b90d65fabd410","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f1a8846e06388113dfdbb89dee005083fa9afdf9","name":"https://git.kernel.org/stable/c/f1a8846e06388113dfdbb89dee005083fa9afdf9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-90206","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90206","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3e980f5995e0bb4d86fef873a9c9ad66721580d0 2c23fc91789dfd9db746edb3ae9b90d65fabd410 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3e980f5995e0bb4d86fef873a9c9ad66721580d0 f1a8846e06388113dfdbb89dee005083fa9afdf9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.1","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.1 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.6 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/nvme/target/admin-cmd.c","drivers/nvme/target/core.c","drivers/nvme/target/fabrics-cmd.c","drivers/nvme/target/nvmet.h","drivers/nvme/target/pci-epf.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"2c23fc91789dfd9db746edb3ae9b90d65fabd410","status":"affected","version":"3e980f5995e0bb4d86fef873a9c9ad66721580d0","versionType":"git"},{"lessThan":"f1a8846e06388113dfdbb89dee005083fa9afdf9","status":"affected","version":"3e980f5995e0bb4d86fef873a9c9ad66721580d0","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/nvme/target/admin-cmd.c","drivers/nvme/target/core.c","drivers/nvme/target/fabrics-cmd.c","drivers/nvme/target/nvmet.h","drivers/nvme/target/pci-epf.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.1"},{"lessThan":"6.1","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"6.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.1","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix max_qid race between configfs and controller allocation\n\nThe function nvmet_subsys_attr_qid_max_store() can race against\nnvmet_alloc_ctrl() when a subsystem's max_qid limit is modified.\n\nSuppose max_qid is currently 64. If nvmet_alloc_ctrl() executes:\nctrl->sqs = kzalloc_objs(struct nvmet_sq *, subsys->max_qid + 1);\nand at this exact point, a userspace process changes max_qid to 128,\nnvmet_subsys_attr_qid_max_store() will set the new max_qid value. It\nattempts to delete active controllers to force a reconnect, but the\nnew controller won't be deleted because it hasn't been added to the\nsubsys->ctrls list yet.\n\nnvmet_alloc_ctrl() then proceeds and adds the new controller to the\nsubsys->ctrls list. Later, when nvmet_install_queue() is called, it\nwill see max_qid set to 128, but the memory allocated for sqs is only\nsized for 64 entries. This results in a KASAN out-of-bounds warning\nand potential memory corruptions.\n\nFix this by protecting the queue allocations and list insertion in\nnvmet_alloc_ctrl() with down_read(&nvmet_config_sem). Because\nnvmet_subsys_attr_qid_max_store() acquires down_write(&nvmet_config_sem)\nto modify the attribute, this safely prevents the configfs writer from\nmodifying max_qid during controller creation.\n\nCopy the max_qid from the subsystem to the controller's structure\nduring the allocation; ctrl->max_qid never changes as long as the\ncontroller remains in LIVE state, so this will prevent similar race\nconditions."}],"providerMetadata":{"dateUpdated":"2026-09-17T16:07:22.173Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/2c23fc91789dfd9db746edb3ae9b90d65fabd410"},{"url":"https://git.kernel.org/stable/c/f1a8846e06388113dfdbb89dee005083fa9afdf9"}],"title":"nvmet: fix max_qid race between configfs and controller allocation","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-90206","datePublished":"2026-09-17T16:07:22.173Z","dateReserved":"2026-09-11T19:38:34.793Z","dateUpdated":"2026-09-17T16:07:22.173Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-17 17:17:15","lastModifiedDate":"2026-09-17 17:17:15","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"90206","Ordinal":"1","Title":"nvmet: fix max_qid race between configfs and controller allocati","CVE":"CVE-2026-90206","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"90206","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix max_qid race between configfs and controller allocation\n\nThe function nvmet_subsys_attr_qid_max_store() can race against\nnvmet_alloc_ctrl() when a subsystem's max_qid limit is modified.\n\nSuppose max_qid is currently 64. If nvmet_alloc_ctrl() executes:\nctrl->sqs = kzalloc_objs(struct nvmet_sq *, subsys->max_qid + 1);\nand at this exact point, a userspace process changes max_qid to 128,\nnvmet_subsys_attr_qid_max_store() will set the new max_qid value. It\nattempts to delete active controllers to force a reconnect, but the\nnew controller won't be deleted because it hasn't been added to the\nsubsys->ctrls list yet.\n\nnvmet_alloc_ctrl() then proceeds and adds the new controller to the\nsubsys->ctrls list. Later, when nvmet_install_queue() is called, it\nwill see max_qid set to 128, but the memory allocated for sqs is only\nsized for 64 entries. This results in a KASAN out-of-bounds warning\nand potential memory corruptions.\n\nFix this by protecting the queue allocations and list insertion in\nnvmet_alloc_ctrl() with down_read(&nvmet_config_sem). Because\nnvmet_subsys_attr_qid_max_store() acquires down_write(&nvmet_config_sem)\nto modify the attribute, this safely prevents the configfs writer from\nmodifying max_qid during controller creation.\n\nCopy the max_qid from the subsystem to the controller's structure\nduring the allocation; ctrl->max_qid never changes as long as the\ncontroller remains in LIVE state, so this will prevent similar race\nconditions.","Type":"Description","Title":"nvmet: fix max_qid race between configfs and controller allocati"}]}}}