Linux kernel vulnerability in eBPF sockmap impacts widely deployed OS kernels and cloud/host networking; can disrupt infrastructure and enable kernel compromise.
CVE-2026-64548
Linux kernel bpf/sockmap integer overflow leads to out-of-bounds memcpy.
Is CVE-2026-64548 being exploited?
Not confirmed. CVE-2026-64548 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.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-64548?
CVE-2026-64548 is rated High with a CVSS score of 8.4. 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-64548?
Yes. A fix has been recorded for CVE-2026-64548. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64548 affect?
CVE-2026-64548 affects Linux kernel (bpf/sockmap), Hosts/VMs using eBPF networking, Containers/network appliances running vulnerable kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64548?
Install vendor kernel security updates and restrict untrusted BPF access; backport fixes if needed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted BPF input can trigger undersized allocation and OOB memcpy, causing kernel memory corruption leading to crash, local privilege escalation or arbitrary kernel compromise.
Immediate action required
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < f1644c9508d24f50dd9e8ebe8d3ba86e0996d2f5
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < a12b1575f9feabd91695a9e9d004862f7195fa25
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < ff39d0e3b4feeb65ca43c453d7c75fdf872ded0d
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < 888706a76286c547bd035432602571e8024b5305
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < db77b6bb6e6edb79b10b4efcce346eec5582d588
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < 4e40056bb5c829f0423f0a6694a0477726d2147e
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < bd004716ba75fed6d185795c85cdc92540ebeaab
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < 0c0a8ed85349dae298712d79cb276acfeb794d82
- affected4.20
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.