From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154291; b=Oh3nZ3zVpwOknpVxEgx3ffXSjfvulOYQc7Oe9k3mHuot+DjKbAcka0+CK3l7Blshu/VG diMYQDhGOWXOkx/5Lo7g3dE/dGY8XSgVVkz3o932zjfSyJTE7p79Mix4SHOMYVSJ9Pu7S dk36EMD/EbOxMGGtOSSsJUJLgtZ6MM4iSJWEonOB7cZJ0hZWZYli173SpyAoENsbZjJWy +qzp8hfNZae/uQdmoHHQ92xM2JJcIcKVCWTr08IocJ0+Cz1XsmZq47gZL5C2oFdgj9Q4V OLWMYdzy9FNcun348G10pzKlyVrrxQRvf31AO53w9HlIrWHklkP1QgjL9XpOQMvPuKg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154291; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=arQ4q5+I0Z3dXcYkKXt2t+IF6tXaRZ0xQAtMg6F3tXs=; b=00uKli2m5OqGUz3k8X45qJ8h5+D3EoK1pQMMUOzv2jmNo/BSY0wGjsDbE73dB+SK4g3u qiBp8znEvfwuHJfw1Cz5dnWAT/mLHZA6XWvWGOMGGY7VN/MVnk3iarRVdEo4E8mJQjLNl r9m1Xs0uJIJ4NSKVoXQb6177xU1KdZtKQXRHw5CyLidXvnTjwyJDArZFtlKaCchLHnXRd 9Q6mU0KlTLs5zZiZObAhMUS5scJzeIIQ4qVFwyFhlkBRZ/evcP2JgHdTMq/J6NLwvYgz0 9GufQw/NU7C9BPDsbBYNJlGBuqNpww9jn/UsRLWO7Ai9E4qamq2gx+acvtFiP0wo5Gg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=uP9V2RW4; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 94FE760A2602 for ; Fri, 20 Nov 2026 05:58:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=uP9V2RW4 Received: by smtp.kernel.org (Postfix) with ESMTPSA id D4F671F000EE; Fri, 20 Nov 2026 05:58:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154291; bh=arQ4q5+I0Z3dXcYkKXt2t+IF6tXaRZ0xQAtMg6F3tXs=; h=From:To:Cc:Subject:Date:Reply-To; b=uP9V2RW4apqgCVPiflUu64aMGaF63GziPfH8UrdVdLMSlnwRVZg6wnh9oHat2yauf hhxoRJG7IXmusVPekE1qaiOga3MtQsBHlfUpDxGHFrBGzxPkPrDUtFukg0bcPzjaOe IUT0/qfPUofEFxX1nDsIAcPl+AtRMrWJPHZ5xl+8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99675: nvmet: reject keep-alive timeouts that would overflow Date: Fri, 20 Nov 2026 06:51:01 +0100 Message-ID: <2026112052-CVE-2026-99675-ba59@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3076; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=zUyLja0c/RZikRU2rhXfYkfU+TDkQ7UIRTkAGd1jMdg=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7zeE/JxZcNW6L3qi2pJZjQePf/PnuSljf4J50a4Jq jfuhS237YhlYRBkYpAVU2T5so3n6P6KQ4pehranYeawMoEMYeDiFICJpFgyLGjo7Su5WjJ7ni3f ntecP+5uDkgMM2FY0C8Vvn/iIYZ6rQnlM2/Jl51tuC29DgA= 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: nvmet: reject keep-alive timeouts that would overflow nvmet_set_feat_kato() and nvmet_alloc_ctrl() convert the 32-bit millisecond KATO from the host to seconds with DIV_ROUND_UP(kato, 1000). The addition in DIV_ROUND_UP() is done in 32 bits, so any KATO above 4294966296 ms wraps around and rounds to 0 seconds. A Set Features command with KATO 0xffffffff then succeeds but disables the keep-alive timer: Get Features returns 0 and Keep Alive fails with Keep Alive Timeout Invalid. A Connect command with such a KATO creates a controller without a keep-alive timer. The converted value has more consumers that can overflow. Get Features multiplies it by 1000, and the timer paths multiply it by HZ in 32 bits and arm a delay that must not exceed MAX_JIFFY_OFFSET. Reject a KATO whose rounded value does not fit all of these. Return Keep Alive Timeout Invalid from both Set Features and Connect. Validate Set Features before stopping the current timer so a failed update leaves its timeout unchanged. Round in 64 bits. A KATO of 0 keeps its current meaning. The Linux kernel CVE team has assigned CVE-2026-99675 to this issue. Affected and fixed versions =========================== Issue introduced in 4.8 with commit a07b4970f464f13640e28e16dad6cfa33647cc99 and fixed in 6.18.64 with commit 69d4f0ace16c7ff00ff525152aed1383f82b1192 Issue introduced in 4.8 with commit a07b4970f464f13640e28e16dad6cfa33647cc99 and fixed in 7.3.5 with commit 884b47ced96c01e2689ee45dc42902d888c4b7f2 Issue introduced in 4.8 with commit a07b4970f464f13640e28e16dad6cfa33647cc99 and fixed in 7.4-rc2 with commit 96ae13f40ce5930cd58c43128e385131476f2a66 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-99675 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/target/admin-cmd.c drivers/nvme/target/core.c drivers/nvme/target/nvmet.h 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/69d4f0ace16c7ff00ff525152aed1383f82b1192 https://git.kernel.org/stable/c/884b47ced96c01e2689ee45dc42902d888c4b7f2 https://git.kernel.org/stable/c/96ae13f40ce5930cd58c43128e385131476f2a66