Affects the Linux kernel's Geneve handling — widely deployed in servers, cloud and virtualization; can enable remote kernel compromise and widespread disruption.
CVE-2026-72407
Linux kernel Geneve GRO bug allows remote-triggered kernel memory corruption.
Is CVE-2026-72407 being exploited?
Not confirmed. CVE-2026-72407 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.52% probability of exploitation in the next 30 days.
How severe is CVE-2026-72407?
CVE-2026-72407 is rated Critical with a CVSS score of 10.0. 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-72407?
Yes. A fix has been recorded for CVE-2026-72407. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72407 affect?
CVE-2026-72407 affects Linux kernel (geneve module), Cloud hypervisors (KVM/libvirt) using Geneve, Network virtualization platforms. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72407?
Apply vendor/kernel updates immediately; block Geneve traffic until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote-crafted Geneve packets can cause out-of-bounds kernel memory access, enabling crashes, privilege escalation, or remote kernel code execution.
Immediate action required
- affected>= fd0dd796576e1a560e1441e665810129f0a82be0 and < e2087447f562692ff0cd08a0554d8d4ad083aa5c
- affected>= fd0dd796576e1a560e1441e665810129f0a82be0 and < cbb0d30a1ad6fc9439b1dc9b4f5a7a9140d3b11f
- affected7.0
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.