Skip to content
major vulnerability· requires attention

Affects the Linux kernel eBPF verifier — core infrastructure used across organizations; exploit could enable kernel memory access or escalation.

Systems

CVE-2026-72426

8.4
High
EPSS 0.18%Patch availableAug 17, 2026

Linux eBPF verifier bug can bypass pointer checks, risking kernel memory access.

common questions

Is CVE-2026-72426 being exploited?

Not confirmed. CVE-2026-72426 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-72426?

CVE-2026-72426 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-72426?

Yes. A fix has been recorded for CVE-2026-72426. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72426 affect?

CVE-2026-72426 affects Linux kernel (eBPF verifier), Linux distributions with affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72426?

Apply vendor kernel updates and restrict untrusted eBPF programs; enable mitigations.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (eBPF verifier)Linux distributions with affected kernels
impact

Crafted eBPF programs can bypass pointer verification leading to kernel memory disclosure and potential privilege escalation or kernel compromise.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= be23266b4a08540aa43d8503a2ea10247c8daebe and < 0f9278b22cda6fd2525049930157b79b4036b4ef
  • affected>= be23266b4a08540aa43d8503a2ea10247c8daebe and < 3a354149bceacadbcf7d7b4766f5ef26a85892ab
  • affected7.1
vendor says fixed in< 7.1, >= 7.1.5 and <= 7.1.*, >= 7.2 and <= *

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free