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=1795154071; b=sSPv6RaQ+1bZ+/cT5FDsCdmgRfax15K+eZqnxaxWLpBaRqZNb9sL0mQ/I6PxZjjHsAAr jdVDzGEgvo5L/cQxmsG1+PjTsR083vU4RQ4sNzwD13rSNvkAPYQOO+k9+9oAqCqEk0rJg JAlabHGsSm4aVU6iAtSsCEqto5wtD3Aee4xTHstdlnOYTKr3yX6FEHhx/5kVQYYjhPvuU TRd4I6/U/pwRpVTgSBDuxG+qzOgHSEnvHvQ5ZsMhA9KIphYxYrtmq/X/FwDZPqIlGq5TR JDfV4prgD6us9iXqKybtiUUG3pSjYHbhKxJ71auWmC+u0Aqn6JhO/ZwTTcziy+o9epg== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154071; 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=lXGMnKtXFaG16XK8BhvXXQXbauZxItX4Y1BAAXnOdA8=; b=VWBqKcG2fvb+7emLVjivLPqc9b+oUTu5H8bePvcyBgnZhcisQ3nCCYnBp0qC69Sg2h2j 1eiYo6rtPJYtVfILUzEYkOIqXvahURHVRXBUsiL7+o893K/16MSwWRAiUiSWL3xgLrKQf wnev2fzBRIFu9i+ngYqPy/AX3h0VcV3RSgP0UUeWWAvOSFG1HCRAhoeLsaosLPUxENjtv Gah6aVkD9zab6tWr11m7ak6yA8jc1r6UeVGjo1RxHjMJ+PUQyH79y68Jdun6RXXUZszoX qtkESA0G49dB1Z4Z+bNmQUJDN/doWQc1hfLk034W9NCsC4tnN7/8Ntnyc3hLa1Ckj9g== 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="eQl36/1o"; 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 51A2E606A320 for ; Fri, 20 Nov 2026 05:54: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=eQl36/1o Received: by smtp.kernel.org (Postfix) with ESMTPSA id A10171F000C4; Fri, 20 Nov 2026 05:54:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154071; bh=lXGMnKtXFaG16XK8BhvXXQXbauZxItX4Y1BAAXnOdA8=; h=From:To:Cc:Subject:Date:Reply-To; b=eQl36/1oL7FPVyJby+ZORFM98Z+z02OruPbaB1VznfKBsNFadxNGk4FGu5iVw+/me 5DnIc7f6y5xrP/7tFXq+3lRCzqpFTJQaPw8JsZ1OWYxOLh4Zl+IWSlof9rP5Bg4HFc zA9uBWsR3yj9TElilqKMlxMoMJF0CRtNt/MBPmFI= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99615: l2tp: only return sessions of the given tunnel in l2tp_session_get() Date: Fri, 20 Nov 2026 06:50:01 +0100 Message-ID: <2026112031-CVE-2026-99615-a693@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=3814; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=NNc71YLMopNzR3a8EHBD3NLoTebE5X0/9pJWcz1HgiI=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/72cX6NQ0Hn0v+kavQecJ5+ryPVw8HopCYidn7dvNs CdKfM+HjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZiIsi7DfIebD1w6N8v0zj/f fOlCnvzLzYWlmxgWHNq26vgM/RvGz+6/yV7KO5PxyyFOBQA= 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: l2tp: only return sessions of the given tunnel in l2tp_session_get() Commit 5f77c18ea556 ("l2tp: use IDR for all session lookups") made pppol2tp_connect() and the netlink session commands find sessions with l2tp_session_get(), passing the socket of the tunnel they name. L2TPv3 session IDs are unique per network namespace, except that sessions carried over UDP are only unique per UDP socket, the socket of their tunnel. However, l2tp_v3_session_get() only checks the socket when another session has the same session ID. Otherwise it returns the session, whichever tunnel it belongs to. As of now, a session command that names the wrong tunnel acts on a session of another tunnel, and a PPPoL2TP socket for a second L2TPv3 tunnel fails with EEXIST, because it finds session 0 of the first tunnel. The issue can be reproduced with: ip l2tp add tunnel tunnel_id 3 peer_tunnel_id 3 encap udp \ local 127.0.0.1 remote 127.0.0.1 udp_sport 5003 udp_dport 6003 ip l2tp add tunnel tunnel_id 4 peer_tunnel_id 4 encap udp \ local 127.0.0.1 remote 127.0.0.1 udp_sport 5004 udp_dport 6004 ip l2tp add session tunnel_id 3 session_id 7 peer_session_id 7 ip l2tp del session tunnel_id 4 session_id 7 ip l2tp show session Before that commit, the delete fails with "No such device", and session 7 of tunnel 3 is still listed. After that commit, the delete succeeds, and session 7 of tunnel 3 is gone. This patch will make l2tp_session_get() return NULL when the L2TPv3 session it finds does not belong to the given socket. The receive path calls l2tp_v3_session_get() directly and is not changed. The Linux kernel CVE team has assigned CVE-2026-99615 to this issue. Affected and fixed versions =========================== Issue introduced in 6.11 with commit 5f77c18ea55601822f9c495135a5b5d4b499d647 and fixed in 6.12.118 with commit 649d00a0e1ff2f5a4f5b8c194755f9b9bbd98504 Issue introduced in 6.11 with commit 5f77c18ea55601822f9c495135a5b5d4b499d647 and fixed in 6.18.64 with commit 26cb789c98bdd4dcc2af6e083eeaa23c4d8715c4 Issue introduced in 6.11 with commit 5f77c18ea55601822f9c495135a5b5d4b499d647 and fixed in 7.3.5 with commit 2dec8c5a6928f27a40e8880df2af3289693abbcd Issue introduced in 6.11 with commit 5f77c18ea55601822f9c495135a5b5d4b499d647 and fixed in 7.4-rc2 with commit a75facf4bb3e866103ddca4f47a6f3ca4b090d8b 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-99615 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/l2tp/l2tp_core.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/649d00a0e1ff2f5a4f5b8c194755f9b9bbd98504 https://git.kernel.org/stable/c/26cb789c98bdd4dcc2af6e083eeaa23c4d8715c4 https://git.kernel.org/stable/c/2dec8c5a6928f27a40e8880df2af3289693abbcd https://git.kernel.org/stable/c/a75facf4bb3e866103ddca4f47a6f3ca4b090d8b