Skip to content
CVSS 10.0CVSS 10.0 · CRITICAL

CVE-2026-74475Corrupcion de memoria en VXLAN del kernel de Linux

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.

Ver en NVD

Análisis

Esta vulnerabilidad critica en el kernel de Linux afecta el modulo VXLAN, permitiendo condiciones de carrera que pueden resultar en la lectura de direcciones MAC corruptas. Afecta directamente a entornos que utilizan redes virtualizadas, incluyendo implementaciones de Docker y Kubernetes en la nube. Es imperativo actualizar el kernel para mitigar riesgos de inestabilidad y posibles ataques a la integridad de la red.

Roles relevantes

LinuxDockerKubernetesCloudCyberSecurityBackend

Severidad

Puntaje: 10.0(CRITICAL)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
AV: NETWORK
AC: LOW
PR: NONE
UI: NONE
S: CHANGED
C: HIGH
I: HIGH
A: LOW

EPSS

Probabilidad de explotación (próx. 30 días): 0.0040 (0.4%)
Percentil: 33.2%
EPSS: 2026-08-19

Descripción técnica

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.

Publicada: 15/8/2026, 13:17:52
Última modificación: 19/8/2026, 17:21:04

Referencias

InicioEventosBlogRecursosCursosEquipo