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=1795099651; b=Me/ZXpeyR8NHrWbvmazDKVq0APOHiOzl6D3kow8RYTNM+AxE4eJD75tbBiPHL76gSboO K70XIIxCNQHauryhhR4p7adOup2PlbD39WHRn110gfnoW3ep4n8d1hCAoIZViA3kMWjb4 rm6lw/LufL9ZbsykD1x6Cs23id74ZNat3C/VpMCwBBtjxpLg1tBdsjj3mYFYgcjPtB/fd tbFSVs4GQu9BnsdiArin+fJmFaf7vcW2UUILEWN6CyfGPHZMQ3RVUUrNAm3nhl7CCArsm cMXtyfytTFV/qqrAsDbxZPGhTp4fNDRKjlZZ/FKp4ViCujtmJPZheYAEzgk8zG2Intw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795099651; 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=zohXdygaPiabHS1iYpHlgb1xNeFAG/bYoaoDjfFc0oI=; b=0eIThywaae0TqJ48eEc1wacuDegFbRYPeafqIjmKY+6Vn4EvEKEVVfuqRVJaeLaQDa0K m13S20uo7KXn1yb+m1d5SLVgHoqN1keH2r5XsYqDF/uhena2VWLtZn1buNKdPTyDoEN3i hYFdaHb6O/gxWZYo3Y6bsrPHqX2/UOSoGyeIyei0/yFugisGS/XH650RpQcN59cPpqxpH lVhUsDXZysn0DLCuwAPSXb0V0yMF4FQUR3vWHXPQFM+3Mh6XQMa0zplfmlZMzVmKAGP0k DM4B8Vn+jqkbNgzqjcwLPZz6z8JiYuxzQ/6tU9CoX5tWdoxUWgZ5wrvEQ9LcCvfhaaw== 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=V8CkS87g; 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 DE54D606A324 for ; Thu, 19 Nov 2026 14:47:31 +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=V8CkS87g Received: by smtp.kernel.org (Postfix) with ESMTPSA id 463B11F000C5; Thu, 19 Nov 2026 14:47:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795099651; bh=zohXdygaPiabHS1iYpHlgb1xNeFAG/bYoaoDjfFc0oI=; h=From:To:Cc:Subject:Date:Reply-To; b=V8CkS87gvDwfejVSGnyBg5bTdWEv6rMl0clBLe38xoxfJCwAiNHme5vISgmFnMyEt et1wZ/2PMM+L0h3Mj3utFnd38iK8ggID9/suecDkHFVR1Z0qIy/aAD9Doyj0w4RU/I r3vDh1U8BPm4MeYlPKISIfkAT9RZn5JQhY1UcToc= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99402: netfilter: nft_payload: restrict checksum offsets to known values Date: Thu, 19 Nov 2026 15:25:00 +0100 Message-ID: <2026111957-CVE-2026-99402-ebeb@gregkh> X-Mailer: git-send-email 2.56.0 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=2279; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=cUBZnS8BTRMwycDHG6LFTRThqJRSg17HR5A2a13eaZs=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2WrVn8W97NMLuzXhTsKmaV4Pv3I/9Gr12Kn48tr6N /na+3+864hlYRBkYpAVU2T5so3n6P6KQ4pehranYeawMoEMYeDiFICJcOcwzJV41fQrSDAx6NOn fZujzXzP5CxS6GGYp1px+lWA1US7Wa9F7a53zlKsOzdvDQA= 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: netfilter: nft_payload: restrict checksum offsets to known values We need to prevent userspace from corrupting e.g. tcp->doff, because many locations in conntrack and conntrack helpers rely on nf_conntrack_in() having validated the packet headers. nft_payload allows to alter headers later which invalidates this assumption. The 'Fixes' commit restricts writes to safe fields, but there is another side channel: the checksum location. Restrict this too. Reported via sashiko/gemini. The Linux kernel CVE team has assigned CVE-2026-99402 to this issue. Affected and fixed versions =========================== Issue introduced in 7.3 with commit 112e447d17f78d08485b3076a8baa1dfb9794bd8 and fixed in 7.3.2 with commit e81a69d22ae06c1cbb211f3301641f332d74f83e Issue introduced in 7.3 with commit 112e447d17f78d08485b3076a8baa1dfb9794bd8 and fixed in 7.4-rc1 with commit c2226f0c7fe90b67732e5ae36dc5c3cc01ddf888 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-99402 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: net/netfilter/nft_payload.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/d1f2c892c6cb5801a51817b12bd0326b22b27880 https://git.kernel.org/stable/c/e81a69d22ae06c1cbb211f3301641f332d74f83e https://git.kernel.org/stable/c/c2226f0c7fe90b67732e5ae36dc5c3cc01ddf888