Linux kernel veth/XDP bug affects container and host networking (widely deployed). Can leak kernel memory and enable crashes or privilege escalation across many orgs.
CVE-2026-74612
Linux veth/XDP skb-length bug leaks kernel memory and can lead to crash/escalation.
Is CVE-2026-74612 being exploited?
Not confirmed. CVE-2026-74612 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-74612?
CVE-2026-74612 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-74612?
Yes. A fix has been recorded for CVE-2026-74612. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74612 affect?
CVE-2026-74612 affects Linux kernel (veth/XDP), Containers using veth (Docker, Kubernetes), Virtualization hosts using veth. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74612?
Apply vendor kernel updates, reboot hosts, restrict XDP/veth exposure until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted UDP via veth+XDP causes out‑of‑bounds kernel->userspace copy leaking kernel pointers/data; may crash, enable info disclosure and potential privilege escalation/RCE.
Immediate action required
- affected>= 718a18a0c8a67f97781e40bdef7cdd055c430996 and < 0c3024afabb8064b141f3cedcb1ddd6ab05ad9d5
- affected>= 718a18a0c8a67f97781e40bdef7cdd055c430996 and < 2f2a7f3f8b9f1bffc9b0488aa02b6951b2aec139
- affected>= 718a18a0c8a67f97781e40bdef7cdd055c430996 and < 41b96667d42b74bb4b137f1bb78b611a953c5943
- affected>= 718a18a0c8a67f97781e40bdef7cdd055c430996 and < cdf745b7a777f87f51666e5d8f4c6fc279bcf54d
- affected>= 718a18a0c8a67f97781e40bdef7cdd055c430996 and < 3205b0652a37255dbb7ca8f3d942c8d8aa677c21
- affected>= 718a18a0c8a67f97781e40bdef7cdd055c430996 and < cb6379feaaff11c4e1e79c26c745ffa23182768a
- affected5.18
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.