Linux kernel is core infrastructure; a remote kernel memory-corruption/RCE impacts servers, cloud, edge and networking devices broadly.
CVE-2026-74616
Linux kernel XDP clone bug allows kernel memory corruption and potential RCE.
Is CVE-2026-74616 being exploited?
Not confirmed. CVE-2026-74616 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.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-74616?
CVE-2026-74616 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-74616?
Yes. A fix has been recorded for CVE-2026-74616. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74616 affect?
CVE-2026-74616 affects Linux kernel (XDP/eBPF-enabled builds), Network-facing Linux servers, Edge routers/NFV appliances, Cloud instances using XDP. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74616?
Apply vendor kernel/security updates or backport patch and limit XDP exposure.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote kernel memory corruption via crafted XDP packets, potentially enabling kernel-level code execution or privilege escalation.
Immediate action required
- affected>= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 and < 58408982fa39f9758124cec169f42854d6f98f35
- affected>= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 and < 685edea27ac68d08fe4dbd3de74b858d2ad8e830
- affected>= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 and < ba13763d667e008e185fedf592d53846a5b457d1
- affected>= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 and < ef4b7c7046d29a67090de15af0da0d1ae8d1b192
- affected>= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 and < fab820f1691a9e26d9031f18aae1e9ce09078f92
- affected>= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 and < f463b6f4957c9c3fd1c75f8d3e5af4879fa609c0
- affected>= e624d4ed4aa8cc3c69d1359b0aaea539203ed266 and < e48e8edbef2eb824201495daa5234560f632b23c
- affected5.14
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.