Linux Kernel up to 7.2-rc5 vxlan route_shortcircuit race condition

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$0-$5k0.48

Summaryinfo

A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 6.6.150/6.12.102/6.18.43/7.1.7/7.2-rc5. The affected element is the function route_shortcircuit of the component vxlan. Performing a manipulation results in race condition. This vulnerability is known as CVE-2026-74475. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability classified as very critical has been found in Linux Kernel up to 6.6.150/6.12.102/6.18.43/7.1.7/7.2-rc5. This affects the function route_shortcircuit of the component vxlan. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: vxlan: use neigh_ha_snapshot() in route_shortcircuit() The neighbour hardware address n->ha can be updated asynchronously by the neighbour subsystem, protected by n->ha_lock seqlock. Reading n->ha without holding the seqlock loop can lead to torn reads or reading a partially updated MAC address. Use neigh_ha_snapshot() in route_shortcircuit() to safely copy n->ha under read_seqbegin()/read_seqretry() lock protection before using it. Note that arp_reduce() and neigh_reduce() seem to have the same issue left for future patches.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-74475 since 08/15/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/15/2026).

Upgrading to version 6.6.151, 6.12.103, 6.18.44, 7.1.8 or 7.2-rc6 eliminates this vulnerability. Applying the patch d08e8ac13f2e228cc7fc3c70b5ebe71557b624a0/ec341bb76d77b4c2948764375ee6bfeef4bb41c3/ff89415d34c3ab9f5312316423122e664ed3524f/05f2987f73daa05333fd713d05546142f9f7c5f0/8eca411347e1d38964f9ed2c8d3b6ab0e7e4473d is able to eliminate this problem.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

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: Race condition
CWE: CWE-362
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.6.151/6.12.103/6.18.44/7.1.8/7.2-rc6
Patch: d08e8ac13f2e228cc7fc3c70b5ebe71557b624a0/ec341bb76d77b4c2948764375ee6bfeef4bb41c3/ff89415d34c3ab9f5312316423122e664ed3524f/05f2987f73daa05333fd713d05546142f9f7c5f0/8eca411347e1d38964f9ed2c8d3b6ab0e7e4473d

Timelineinfo

08/15/2026 Advisory disclosed
08/15/2026 +0 days CVE reserved
08/15/2026 +0 days VulDB entry created
08/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-74475 (🔒)
GCVE (CVE): GCVE-0-2026-74475
GCVE (VulDB): GCVE-100-390825

Entryinfo

Created: 08/15/2026 15:28
Changes: 08/15/2026 15:28 (59)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!