CVE-2026-74474
Linux kernel VXLAN header-pull bug allows kernel memory access or crash.
Is CVE-2026-74474 being exploited?
Not confirmed. CVE-2026-74474 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-74474?
CVE-2026-74474 is rated Critical. 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-74474?
Yes. A fix has been recorded for CVE-2026-74474. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74474 affect?
CVE-2026-74474 affects Linux kernel (vxlan module), Linux hosts with VXLAN enabled, Cloud hypervisors and network appliances using VXLAN. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74474?
Apply Linux kernel update that includes the vxlan pskb_network_may_pull() fix immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted VXLAN packets can trigger out-of-bounds kernel memory access, causing crashes, info leaks, or potential kernel code execution.
Immediate action required
- affected>= e4f67addf158f98f8197e08974966b18480dc751 and < bb01c51950c3ff3c76acdd54b85ab38ccc2a8bb4
- affected>= e4f67addf158f98f8197e08974966b18480dc751 and < 6146901881f09ef063eb34ad389f63231f8486f5
- affected>= e4f67addf158f98f8197e08974966b18480dc751 and < 94dee751aad627b3645d424b5d0c736d394573e9
- affected>= e4f67addf158f98f8197e08974966b18480dc751 and < 7076a34b6e33315dc160b4612bfea1c597495585
- affected>= e4f67addf158f98f8197e08974966b18480dc751 and < b9553558b48db54ac9273e6b98d7263ef5c1a329
- affected3.8
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.