CVE-2026-74475
Linux kernel vulnerability
- Published15 Aug 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:LRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/05f2987f73daa05333fd713d05546142f9f7c5f0
- https://git.kernel.org/stable/c/32a9590a8d30426e3db63e6b20893e47e02576c0
- https://git.kernel.org/stable/c/87210054bad82bbae6f483a742dc45722fb47a6b
- https://git.kernel.org/stable/c/8eca411347e1d38964f9ed2c8d3b6ab0e7e4473d
- https://git.kernel.org/stable/c/d08e8ac13f2e228cc7fc3c70b5ebe71557b624a0
- https://git.kernel.org/stable/c/d0993fc053f29e15cc7c9fe2029df3882a2ab5ab
- https://git.kernel.org/stable/c/ec341bb76d77b4c2948764375ee6bfeef4bb41c3
- https://git.kernel.org/stable/c/ff89415d34c3ab9f5312316423122e664ed3524f
Frequently asked
Is CVE-2026-74475 being actively exploited?
CVE-2026-74475 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.45%.
How severe is CVE-2026-74475?
CVE-2026-74475 has a CVSS 3.1 base score of 10.0, rated critical. EPSS estimates a 0.45% probability of exploitation.
How do I fix CVE-2026-74475?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-74475 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.