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 4E65F3C6606 for ; Mon, 10 Aug 2026 12:01:55 +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=1786363317; cv=none; b=cu46yP36shOB0tQ8/PYLcZn/cEuxwgvrMwkpGBp3jlnTaYUTH6cTWVg13w4wVEV8ubZvCSl7WxbBuE1/InfyHZfrCytpeYXASVCTbyJ7Kd4kbhSq0gUXZDv0L9FOU3CymjUubV5IhCreWiihB3tIF3OOCQsZFeCcYW+ZjQyZEAE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786363317; c=relaxed/simple; bh=HYVbrr2T7VpOUhG1DYHDBRish2rOq61AHD3urbKPc3s=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=Yu4nsgZS1cJkV7Vqj6w7X8a4D78MRPTC2R2HACa8ykfyNtpv2nAChFnnBqbJNyxPWsB0/d5la+S2K89y4LUe+0d2VY2uaN151kJhoA2LR8BDcxMdWCSiFLXXrJuBVciuNCeiNnRdoXMC1I2Poz0QtLwu3SfZy2GTJdOqCZiQ74A= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=u/AcpvbM; 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="u/AcpvbM" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6E7D61F000E9; Mon, 10 Aug 2026 12:01:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786363315; bh=oZTTn+enmujG7vLq9QGfPpqSVKhB+vs1Sdb7MaeEg9M=; h=From:To:Cc:Subject:Date:Reply-To; b=u/AcpvbMqchX+azWQ5+drfHvQ2Ls9yG+AMtqoLWce1jNHl0ys73M82PjL6t1Wh6Rx +4fLi3HDRsHdymnz8B3VaTzrWcIpyfOIhqX1E6i6e8ziQMkGSc6WiVCcGF4fzyy+I2 1zeFpdb0Fpws9eT7Xz9FToOIjW/8v4cVFfmN3hhs= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-68116: vxlan: mdb: Fix source list corruption on a failed replace Date: Mon, 10 Aug 2026 13:57:13 +0200 Message-ID: <2026081055-CVE-2026-68116-44c2@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=3910; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=oFngrgeCCRzTvFfzg7kbKa1gN6CFP3ULAAw7Lxwj0Bc=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmVe9o9t6Zx1Pwwz2PXyZVl1V95qefjG/XLyxNrzph5l 5T/kj3XEcvCIMjEICumyPJlG8/R/RWHFL0MbU/DzGFlAhnCwMUpABM5c5thNmuwfMhPjz9vTrqY naw8+XtLwL//CQwzGRkX7VU44XZ+b6GZ5DJeOdadP3abAwA= 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: vxlan: mdb: Fix source list corruption on a failed replace When replacing the source list of an MDB remote entry, all existing sources are first marked for deletion and vxlan_mdb_remote_srcs_add() is then called to add the new source list. Sources present in the new list have their deletion mark cleared, and any sources left marked afterwards are removed. If vxlan_mdb_remote_srcs_add() fails partway through, its error path deletes all entries on the remote's source list. That rollback is only correct for its other caller, vxlan_mdb_remote_add(), where the remote was just allocated and the list contains solely entries added during the call. On the replace path the list also holds pre-existing sources, so a failed replace tears them down together with their (S, G) forwarding entries instead of leaving the entry unchanged. This is reachable from an existing (*, G) remote. An EXCLUDE filter that loses sources starts forwarding traffic that should be blocked, while an INCLUDE filter that loses sources drops traffic that should be forwarded. Mark entries created during the current pass with a new VXLAN_SGRP_F_NEW flag. On failure, delete only those entries and clear the deletion mark on the pre-existing ones, so a failed replace leaves the source list untouched. Retain the flag until the whole operation succeeds and then clear it. Also stop vxlan_mdb_remote_src_add() from deleting a pre-existing entry it only looked up when adding that entry's forwarding entry fails. The Linux kernel CVE team has assigned CVE-2026-68116 to this issue. Affected and fixed versions =========================== Issue introduced in 6.4 with commit a3a48de5eade770e911d35291217bdd69ce04ef1 and fixed in 6.6.148 with commit 5bc8fc1d2ff802eec839e03adef5df597421898d Issue introduced in 6.4 with commit a3a48de5eade770e911d35291217bdd69ce04ef1 and fixed in 6.12.101 with commit 2c54dff57606590fa4abec46bab6bea3133f1539 Issue introduced in 6.4 with commit a3a48de5eade770e911d35291217bdd69ce04ef1 and fixed in 6.18.42 with commit 79370b573e92e8f190eb5f9a511fa5398340d8b2 Issue introduced in 6.4 with commit a3a48de5eade770e911d35291217bdd69ce04ef1 and fixed in 7.1.6 with commit 54a3c27b357dfb34f327f89bfadeb998bef8051e Issue introduced in 6.4 with commit a3a48de5eade770e911d35291217bdd69ce04ef1 and fixed in 7.2-rc5 with commit dcd9b465965422b9654f6026e8a2fa8984f74c3c 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-68116 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/net/vxlan/vxlan_mdb.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/5bc8fc1d2ff802eec839e03adef5df597421898d https://git.kernel.org/stable/c/2c54dff57606590fa4abec46bab6bea3133f1539 https://git.kernel.org/stable/c/79370b573e92e8f190eb5f9a511fa5398340d8b2 https://git.kernel.org/stable/c/54a3c27b357dfb34f327f89bfadeb998bef8051e https://git.kernel.org/stable/c/dcd9b465965422b9654f6026e8a2fa8984f74c3c