From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 25FD31A2C0B for ; Fri, 8 May 2026 13:37:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778247449; cv=none; b=X2AaMizxhjkMkNuVY99Q3TFeJDdXNcxKy5PX65h64WBfpGxoXoPDHCgyJCbpOtCa4zxD+6Vc4XalsthkKeL7VLKORSJEEea0wONheXgro86F3uuv2FZJ8bP70tGapX5OCFkCOpSsdaRJM01rVR3V2VogZg5CIDr3Vf2zhspNKno= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778247449; c=relaxed/simple; bh=AjSoIKP5O3T5SlPDegxo1icD9U1ko0NeWwTYCADjjRQ=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=jPAErwtAgLeGpYTjr/1nfmcpvR2sZBUklNxwq1pZHZdclVTLLeJ1JRZofowXkG+stCsknuG/cZtdlc/lapLLTVVzOz4CCieEOffBc7E75fb5DfzXGB7Pcw3G0tStYA1y3TAe2fuq/qTTJU+0mD9kUG2CiYPh44Kz4cIXLgzAp08= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=r+swVN13; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="r+swVN13" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 718DCC2BCB0; Fri, 8 May 2026 13:37:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1778247448; bh=AjSoIKP5O3T5SlPDegxo1icD9U1ko0NeWwTYCADjjRQ=; h=From:To:Cc:Subject:Date:Reply-To:From; b=r+swVN13FP/0snnio/jc4fIikJtTKNrMh/BEWadjc4eyJu+0WpMc76GVE2ZAUED6+ Cu0kF494zRdvDjB6QICeryn03c09fMIq5Z1gPPO76waQtx7WvCg9QTBpLRUzEwKitR GfXmqcxAzKgTXt23Ow2T584oENHfenSlH1XQMgec= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-43341: net/ipv6: ioam6: prevent schema length wraparound in trace fill Date: Fri, 8 May 2026 15:37:24 +0200 Message-ID: <2026050824-CVE-2026-43341-7c3e@gregkh> X-Mailer: git-send-email 2.54.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=3231; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=OwBup/nH451aWa6Z9JovRq02JoOJi6BexX6noJM7v+0=; b=owGbwMvMwCRo6H6F97bub03G02pJDJl/n4v0PPz/aefhlSc3L5u3q1RLwLnC1pMlINCZ1aulJ DlTW82nI5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACaStJ1hfrz8Z89b+oWfdGU/ 7uZc+M748CHTPwxzRaZdP6C6xOKUlNl612XntVo+zz7zAwA= 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: net/ipv6: ioam6: prevent schema length wraparound in trace fill ioam6_fill_trace_data() stores the schema contribution to the trace length in a u8. With bit 22 enabled and the largest schema payload, sclen becomes 1 + 1020 / 4, wraps from 256 to 0, and bypasses the remaining-space check. __ioam6_fill_trace_data() then positions the write cursor without reserving the schema area but still copies the 4-byte schema header and the full schema payload, overrunning the trace buffer. Keep sclen in an unsigned int so the remaining-space check and the write cursor calculation both see the full schema length. The Linux kernel CVE team has assigned CVE-2026-43341 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15 with commit 8c6f6fa6772696be0c047a711858084b38763728 and fixed in 6.1.168 with commit e96d48b37708d53cbdc47f6f60b0714fc4a5f596 Issue introduced in 5.15 with commit 8c6f6fa6772696be0c047a711858084b38763728 and fixed in 6.6.134 with commit d1b041080086e91d3733a5438a8c51ad5d3d8e09 Issue introduced in 5.15 with commit 8c6f6fa6772696be0c047a711858084b38763728 and fixed in 6.12.81 with commit 77695a69baca9b99d95fad09fc78c2318736604f Issue introduced in 5.15 with commit 8c6f6fa6772696be0c047a711858084b38763728 and fixed in 6.18.22 with commit 184d2e9db27c0f76226b5cad16fe29510a5d2280 Issue introduced in 5.15 with commit 8c6f6fa6772696be0c047a711858084b38763728 and fixed in 6.19.12 with commit d6e1c9b02d85a4f1f4ba6d68e916d9b610a3ed7d Issue introduced in 5.15 with commit 8c6f6fa6772696be0c047a711858084b38763728 and fixed in 7.0 with commit 5e67ba9bb531e1ec6599a82a065dea9040b9ce50 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-43341 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/ipv6/ioam6.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/e96d48b37708d53cbdc47f6f60b0714fc4a5f596 https://git.kernel.org/stable/c/d1b041080086e91d3733a5438a8c51ad5d3d8e09 https://git.kernel.org/stable/c/77695a69baca9b99d95fad09fc78c2318736604f https://git.kernel.org/stable/c/184d2e9db27c0f76226b5cad16fe29510a5d2280 https://git.kernel.org/stable/c/d6e1c9b02d85a4f1f4ba6d68e916d9b610a3ed7d https://git.kernel.org/stable/c/5e67ba9bb531e1ec6599a82a065dea9040b9ce50