From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 78D9B4AA573 for ; Thu, 24 Sep 2026 16:10:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790266244; cv=none; b=Tj3MZ4xJWNoxpWRZIwpTWLZowVe9bT53gE6dD/gjA9awgHG9mmaRmfSwEBh+9h8GEs41Arehlk6xUSG5+Cy8/jW906D21Hd0gxhBH0qZDCJuNcSuVrlqSD2c5wA4s4Nu3RbZGvNrGSTQrV2xgT3HHNV4d9Z/MgiUYrRNK+RLESc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790266244; c=relaxed/simple; bh=PmzmetPKBiHtjnCJ7pMvabVoUoB7V9f5D8MFXLNSSgo=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=YlEk16CKYnQ142OIAWPYKrI0lHTbu4g7xr7M1/uIt6G1jED++kAUvE/kHVzTG/S/GlTOQZquLNVQuTBC10XPDgI4hNhp6zMwxlva3P8c+iP09QaS7NxFSEhcuJVy6EUUeeLm3d2fYxg8vwgMPffXNOolRoBHKhJxOkqXx4tOkoI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=QhTEa//W; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="QhTEa//W" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 12E241F000FF; Thu, 24 Sep 2026 16:10:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1790266243; bh=cUR9S/wQjmaxXy4GYMntyT6tj/zyluOJ7FvWCkh8c98=; h=From:To:Cc:Subject:Date:Reply-To; b=QhTEa//Wl5muWQ3qKpclEHgiRZagivmVojiM7Q43l5w9ZLKBKkvgo8SG3o85uOpVt vhTVigOYB3ZlkTSw5m23oZjtDqjVKlu4huEy2ziyzuk8OFDCwhH5dkCwBjE0w6GVQx 4m/Hfjg8sLzmWQYrukdvbxqYn1OpXmF4LM2UmOaM= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-97409: nvme-fc: Do not cancel requests in io target before it is initialized Date: Thu, 24 Sep 2026 18:03:09 +0200 Message-ID: <2026092425-CVE-2026-97409-0829@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3167; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=BqVZPRE7NFz1rsogokGD6natcmd+wXd5c3JOivC0nq4=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlbPSe+kTxww77N+uZ3qfXqHzSExGJL+z3b9m1nnzl1l /ns6+ZtHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjAR4XMMC7aVKadPEdc6JrXr 02Z5P8nsgm6eIwzzXSrOf/70M+KJxZe/f5/Xr0/Xb05+CwA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: nvme-fc: Do not cancel requests in io target before it is initialized A new nvme-fc controller in CONNECTING state sees admin request timeout schedules ctrl->ioerr_work to abort inflight requests. This ends up calling __nvme_fc_abort_outstanding_ios() which aborts requests in both admin and io tagsets. In case fc_ctrl->tag_set was not initialized we see the warning below. This is because ctrl.queue_count is initialized early in nvme_fc_alloc_ctrl(). nvme nvme0: NVME-FC{0}: starting error recovery Connectivity Loss INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe lpfc 0000:ab:00.0: queue 0 connect admin queue failed (-6). you didn't initialize this object before use? turning off the locking correctness validator. Workqueue: nvme-reset-wq nvme_fc_ctrl_ioerr_work [nvme_fc] Call Trace: dump_stack_lvl+0x57/0x80 register_lock_class+0x567/0x580 __lock_acquire+0x330/0xb90 lock_acquire.part.0+0xad/0x210 blk_mq_tagset_busy_iter+0xf9/0xc00 __nvme_fc_abort_outstanding_ios+0x23f/0x320 [nvme_fc] nvme_fc_ctrl_ioerr_work+0x172/0x210 [nvme_fc] process_one_work+0x82c/0x1450 worker_thread+0x5ee/0xfd0 kthread+0x3a0/0x750 ret_from_fork+0x439/0x670 ret_from_fork_asm+0x1a/0x30 Update the check in __nvme_fc_abort_outstanding_ios() confirm that io tagset was created before iterating over busy requests. Also make sure to cancel ctrl->ioerr_work before removing io tagset. The Linux kernel CVE team has assigned CVE-2026-97409 to this issue. Affected and fixed versions =========================== Fixed in 6.12.111 with commit da930308b4bc24c335574e85ca84ff70a988cf05 Fixed in 6.18.53 with commit dd39064d2948b14dbe4f364fe4b3c9cfc632cc21 Fixed in 7.2 with commit ee38469f88492df99e1d97f03aa40ecfd218934f Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-97409 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/nvme/host/fc.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/da930308b4bc24c335574e85ca84ff70a988cf05 https://git.kernel.org/stable/c/dd39064d2948b14dbe4f364fe4b3c9cfc632cc21 https://git.kernel.org/stable/c/ee38469f88492df99e1d97f03aa40ecfd218934f