{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-90206","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-09-11T19:38:34.793Z","datePublished":"2026-09-17T16:07:22.173Z","dateUpdated":"2026-09-17T16:07:22.173Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-09-17T16:07:22.173Z"},"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."}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","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"],"versions":[{"version":"3e980f5995e0bb4d86fef873a9c9ad66721580d0","lessThan":"2c23fc91789dfd9db746edb3ae9b90d65fabd410","status":"affected","versionType":"git"},{"version":"3e980f5995e0bb4d86fef873a9c9ad66721580d0","lessThan":"f1a8846e06388113dfdbb89dee005083fa9afdf9","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","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"],"versions":[{"version":"6.1","status":"affected"},{"version":"0","lessThan":"6.1","status":"unaffected","versionType":"semver"},{"version":"7.2.6","lessThanOrEqual":"7.2.*","status":"unaffected","versionType":"semver"},{"version":"7.3-rc1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.1","versionEndExcluding":"7.2.6"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.1","versionEndExcluding":"7.3-rc1"}]}]}],"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"}}}}