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 48BD84756C4 for ; Wed, 16 Sep 2026 08:49:20 +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=1789548561; cv=none; b=GKuTX/0DYRu6xnQAZL/sWaN5lDv4TMiozW+yjs+p+vu7hYLlkuYG7S7darAvobTCi9wQdqSBwgXVoqW8rs9U7NDmeGPF0baQCLr2B3Fq6cUGFpIq+Z7UJn/HM37q68Wm4RjaLC/9OCFw2OOSKCFrJb+0gTNFd3D1VJxPTl0Eu1w= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789548561; c=relaxed/simple; bh=qmp62KaXdYxjH6lMlc6ro+t/nDLpfbwaEIQfdNL9+oI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=oye5Ju+kaEMHus9ZwjRXXk5s0CqgD7/MATXtJL0/vSwd40Brju7zdzX6ymrLruM26klQ+2bShqocakfvbdCimA7dQIeQT9ojBKI8xcEVSUd4qpOC6HGR0jxlmc08qu6YwURVfVM+ruLFmzVJnir5/BKiviMq9gBFFljPzVys6xM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=A+8YGdSg; 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="A+8YGdSg" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 939551F000FF; Wed, 16 Sep 2026 08:49:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789548560; bh=UjqEYk4dLiwmFomKxRkeG7IFSrZpB5BvBNg4IJYeUlA=; h=From:To:Cc:Subject:Date:Reply-To; b=A+8YGdSgaeqlZGj7jLNJFVuluMOsH/3On75mlTIh4sVVlBX8G/8a0fAwIrNOZbiia MySPu0KkkQmG33Q6styX9vc58mmVQiDefU/K7c2bNipADttjPa1RRXcil2gouEE7Hs sfbhmU8xGn1vLjv7+SYRVjVUn+Ji4uqwriOZ8GS0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89783: xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full Date: Wed, 16 Sep 2026 09:46:47 +0100 Message-ID: <2026091641-CVE-2026-89783-d43d@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=4127; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=eIqx6PTaxIFhnNRhFmt7qNaXCeIMOwGbh7qr+0jAHfk=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmrwgs/nkxiVZ6l+nn3R5On8vm868X4au2tmz9/MWLc+ u3n0YsSHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjARzT0MC9YoBE45JsqgvnXD /9hN3et2XWqzkWeYp/P3zX5fmxkp2919TqwxnBDsXFe3CwA= 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: xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full The depth check in xfrm6_input_addr() is off by one: if (1 + sp->len == XFRM_MAX_DEPTH) goto drop; ... sp->xvec[sp->len++] = x; xfrm_input() can leave sp->len == XFRM_MAX_DEPTH, and the transport-mode receive path re-enters IPv6 input via xfrm_trans_reinject() with that secpath preserved. If the inner packet carries a destination-options HAO option or a type-2 routing header, xfrm6_input_addr() is called with sp->len == XFRM_MAX_DEPTH; the check (1 + 6 == 6) is false, so sp->xvec[sp->len++] writes one slot past the 6-element xvec[]. The write stays within the sec_path allocation (invisible to KASAN); UBSAN_BOUNDS flags it and panics under panic_on_warn. Use "sp->len >= XFRM_MAX_DEPTH", matching xfrm_input(). This also restores one chain level the old check rejected at sp->len == 5. UBSAN: array-index-out-of-bounds in net/ipv6/xfrm6_input.c:309:10 index 6 is out of range for type 'xfrm_state *[6]' The Linux kernel CVE team has assigned CVE-2026-89783 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.25 with commit 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and fixed in 5.10.270 with commit 91fc387f63c00ddfb5221127a17bac97549a8343 Issue introduced in 2.6.25 with commit 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and fixed in 5.15.221 with commit 68e8737fe8e72f085c608cff322b3d2de8340af1 Issue introduced in 2.6.25 with commit 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and fixed in 6.1.188 with commit 8fe2c53fb81f5ad5be43af2ad09583f7c78b4b77 Issue introduced in 2.6.25 with commit 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and fixed in 6.6.157 with commit bdcda866c89f9a8b1acdabf02d26cde9fbe501d8 Issue introduced in 2.6.25 with commit 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and fixed in 6.12.110 with commit 48996649222e95008cdb98cd58579e3fc8e5ee06 Issue introduced in 2.6.25 with commit 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and fixed in 6.18.52 with commit 0f679e0523ddfff3fb554336ceb874b0e51e9cd3 Issue introduced in 2.6.25 with commit 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and fixed in 7.2.6 with commit 5f35a29a5eed3d80befd32050843ac88dea3d61a Issue introduced in 2.6.25 with commit 9473e1f631de339c50bde1e3bd09e1045fe90fd5 and fixed in 7.3-rc1 with commit 5d9e3bf34fec9a5d237e4b7cef4a707bc2e091bc 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-89783 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/xfrm6_input.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/91fc387f63c00ddfb5221127a17bac97549a8343 https://git.kernel.org/stable/c/68e8737fe8e72f085c608cff322b3d2de8340af1 https://git.kernel.org/stable/c/8fe2c53fb81f5ad5be43af2ad09583f7c78b4b77 https://git.kernel.org/stable/c/bdcda866c89f9a8b1acdabf02d26cde9fbe501d8 https://git.kernel.org/stable/c/48996649222e95008cdb98cd58579e3fc8e5ee06 https://git.kernel.org/stable/c/0f679e0523ddfff3fb554336ceb874b0e51e9cd3 https://git.kernel.org/stable/c/5f35a29a5eed3d80befd32050843ac88dea3d61a https://git.kernel.org/stable/c/5d9e3bf34fec9a5d237e4b7cef4a707bc2e091bc