Skip to content
Networks

CVE-2026-74406

9.8
Critical
EPSS 0.49%Patch availableAug 17, 2026

VXLAN null-pointer race in Linux kernel causes remote kernel crash (DoS).

common questions

Is CVE-2026-74406 being exploited?

Not confirmed. CVE-2026-74406 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.49% probability of exploitation in the next 30 days.

How severe is CVE-2026-74406?

CVE-2026-74406 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-74406?

Yes. A fix has been recorded for CVE-2026-74406. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-74406 affect?

CVE-2026-74406 affects Linux kernel (vxlan module), VXLAN-enabled hosts, hypervisors, SDN overlay endpoints. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74406?

Apply vendor kernel updates and reboot; block VXLAN UDP 4789 from untrusted networks.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (vxlan module)VXLAN-enabled hosts, hypervisors, SDN overlay endpoints
impact

Remote kernel crash (Denial of Service) via crafted VXLAN/UDP packets causing null-pointer dereference in vxlan_gro_prepare_receive.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 5602c48cf87562c2f95b831d690631935e834295 and < 9c58c729d32e7cea5772cc44929c6cd61e5a31cd
  • affected>= 5602c48cf87562c2f95b831d690631935e834295 and < f79c80f173fda9545b220c1f094b65fc06c252d0
  • affected>= 5602c48cf87562c2f95b831d690631935e834295 and < 08f40c0d23c67c3aa4224c3311e134999c721fb4
  • affected>= 5602c48cf87562c2f95b831d690631935e834295 and < 4a8cde6f7281ea2c4c290f9ad9923b3631defceb
  • affected>= 5602c48cf87562c2f95b831d690631935e834295 and < ef44dac2a37f86eeae6b88ed10a6d60b35387dfd
  • affected>= 5602c48cf87562c2f95b831d690631935e834295 and < 30a45c0bffdd62350261e2f2689fdba426a33578
  • affected4.7
vendor says fixed in< 4.7, >= 6.1.178 and <= 6.1.*, >= 6.6.145 and <= 6.6.*, >= 6.12.97 and <= 6.12.*, >= 6.18.40 and <= 6.18.*, >= 7.1.5 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free