CVE-2026-63926
Linux kernel BPF sockmap bug can corrupt kernel memory, enabling crash or local privilege escalation.
Is CVE-2026-63926 being exploited?
Not confirmed. CVE-2026-63926 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.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-63926?
CVE-2026-63926 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-63926?
Yes. A fix has been recorded for CVE-2026-63926. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63926 affect?
CVE-2026-63926 affects Linux kernel (BPF sockmap subsystem), Distributions with upstream/unpatched kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63926?
Install upstream kernel security patch or vendor backport immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Malformed bpf_msg_push_data can corrupt scatterlist layout, leading to kernel memory corruption enabling DoS (crash) or local privilege escalation.
Immediate action required
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < f14609d8146707452e0822f3c8154674ce677251
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < d81b323af2dcee47573907ccb89c0df9b45cb2e2
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < aeb95146848d12206e1b2cfacd4f40e21ce81d94
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < 96b72672ce849a1402730238e64d9b20bf06a96d
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < 3075c21d2d76c0067f4a382765b43d6cc10470f1
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < 5e19028667963fb371ebb00cecc2a473ef92056b
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < 63f64a510c7917658ddf4d073ece73914ee25346
- affected>= 6fff607e2f14bd7c63c06c464a6f93b8efbabe28 and < f72eed9b84fb771019a955908132410a9ba9ea3f
- 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.