CVE-2026-80838
CVE CVE-2026-80838EUVD EUVD-2026-71288Published 2026-09-04T15:54:48.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: vxlan: keep the last remote linked during FDB flush A non-nexthop FDB entry is expected to have at least one remote while it remains reachable through the FDB hash table. A filtered bulk flush violates this invariant when every remote matches: It unlinks the last remote in vxlan_fdb_dst_destroy() and only afterwards tells vxlan_flush() to destroy the parent FDB entry. An RCU reader can find the parent during this interval. first_remote_rcu() then applies list_entry_rcu() to the empty list head, producing an invalid remote pointer that the receive learning path can read from and write to. When a matching remote is the sole remaining remote, leave it linked and ask the caller to destroy the entire FDB entry. vxlan_fdb_destroy() keeps the remote attached while sending the deletion notification and removing the parent from the lookup structures.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 0; patch: 6.12.108; patch: 7.1.13; patch: 7.3-rc1; c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f <8ba68fd6cdd1e3c92b92f25c7e48bf7bd51a183c; c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f <2a7c2f00843225d5f037676bca649321f3d024c7; c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f <d5d4a7b538b52db63927773a8905fcd9f78a42e2; c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f <a8820c8a7718327e96849782033e7c85a0f6bcfe; 6.7; patch: 7.2.3; patch: 6.18.49; c499fccb71cb85902b5c5b9ce9c9ae6683e54a8f <4bbc76ee1b21d3bd045d6d819b2bacd30a6372ab
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.