CVE-2026-68116: 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 vxlanmdbremotesrcsadd() 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 vxlanmdbremotesrcsadd() fails partway through, its error path deletes all entries on the remote's source list. That rollback is only correct for its other caller, vxlanmdbremoteadd(), 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 VXLANSGRPFNEW 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 vxlanmdbremotesrcadd() from deleting a pre-existing entry it only looked up when adding that entry's forwarding entry fails.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68116?
CVE-2026-68116 has a risk rating of 37, indicating a moderate severity level.
How do I fix CVE-2026-68116?
To fix CVE-2026-68116, ensure that your Linux kernel is updated to the latest patched version that addresses this vulnerability.
What systems are affected by CVE-2026-68116?
CVE-2026-68116 affects Linux kernel implementations that utilize vxlan functionality.
What could happen if CVE-2026-68116 is exploited?
If exploited, CVE-2026-68116 could lead to source list corruption in vxlan, potentially disrupting network operations.
Is there a workaround for CVE-2026-68116?
Currently, updating to the latest version of the Linux kernel is the recommended approach, as no specific workarounds have been documented.