Linux Kernel up to 6.12.107/6.18.48/7.1.12/7.2.2 vxlan vxlan_fdb_dst_destroy memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$5k-$25k0.00

Summaryinfo

A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 6.12.107/6.18.48/7.1.12/7.2.2. This affects the function vxlan_fdb_dst_destroy of the component vxlan. This manipulation causes memory corruption. This vulnerability is tracked as CVE-2026-80838. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability classified as very critical was found in Linux Kernel up to 6.12.107/6.18.48/7.1.12/7.2.2. Affected by this vulnerability is the function vxlan_fdb_dst_destroy of the component vxlan. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-80838 since 08/26/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/04/2026).

Upgrading to version 6.12.108, 6.18.49, 7.1.13, 7.2.3 or 7.3-rc1 eliminates this vulnerability. Applying the patch 2a7c2f00843225d5f037676bca649321f3d024c7/a8820c8a7718327e96849782033e7c85a0f6bcfe/8ba68fd6cdd1e3c92b92f25c7e48bf7bd51a183c/4bbc76ee1b21d3bd045d6d819b2bacd30a6372ab/d5d4a7b538b52db63927773a8905fcd9f78a42e2 is able to eliminate this problem.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.108/6.18.49/7.1.13/7.2.3/7.3-rc1
Patch: 2a7c2f00843225d5f037676bca649321f3d024c7/a8820c8a7718327e96849782033e7c85a0f6bcfe/8ba68fd6cdd1e3c92b92f25c7e48bf7bd51a183c/4bbc76ee1b21d3bd045d6d819b2bacd30a6372ab/d5d4a7b538b52db63927773a8905fcd9f78a42e2

Timelineinfo

08/26/2026 CVE reserved
09/04/2026 +9 days Advisory disclosed
09/04/2026 +0 days VulDB entry created
09/04/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80838 (🔒)
GCVE (CVE): GCVE-0-2026-80838
GCVE (VulDB): GCVE-100-398917

Entryinfo

Created: 09/04/2026 18:16
Changes: 09/04/2026 18:16 (59)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!