cveboard RSS feed

CVE-2026-68116

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2026
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

vxlan: mdb: Fix source list corruption on a failed replace

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
a3a48de5eade770e911d35291217bdd69ce04ef1affectedgit5bc8fc1d2ff802eec839e03adef5df597421898dUnavailableNone listed
a3a48de5eade770e911d35291217bdd69ce04ef1affectedgit2c54dff57606590fa4abec46bab6bea3133f1539UnavailableNone listed
a3a48de5eade770e911d35291217bdd69ce04ef1affectedgit79370b573e92e8f190eb5f9a511fa5398340d8b2UnavailableNone listed
a3a48de5eade770e911d35291217bdd69ce04ef1affectedgit54a3c27b357dfb34f327f89bfadeb998bef8051eUnavailableNone listed
a3a48de5eade770e911d35291217bdd69ce04ef1affectedgitdcd9b465965422b9654f6026e8a2fa8984f74c3cUnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
6.4affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver6.4UnavailableNone listed
6.6.148unaffectedsemverUnavailable6.6.*None listed
6.12.101unaffectedsemverUnavailable6.12.*None listed
6.18.42unaffectedsemverUnavailable6.18.*None listed
7.1.6unaffectedsemverUnavailable7.1.*None listed
7.2unaffectedoriginal_commit_for_fixUnavailable*None listed