Skip to content
Networks

CVE-2026-72057

8.2
High
EPSS 0.58%Patch availableAug 17, 2026

Linux kernel net/sched bug: fragmented packets can clear qdisc metadata and trigger kernel WARN/panic.

common questions

Is CVE-2026-72057 being exploited?

Not confirmed. CVE-2026-72057 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.58% probability of exploitation in the next 30 days.

How severe is CVE-2026-72057?

CVE-2026-72057 is rated High with a CVSS score of 8.2. 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-72057?

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

What does CVE-2026-72057 affect?

CVE-2026-72057 affects Linux kernel (net/sched, act_ct, tcf_ct), Systems using kernel network qdiscs/conntrack. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72057?

Apply vendor kernel update and reboot affected hosts immediately.

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

executive summary
technical analysis
affected
Linux kernel (net/sched, act_ct, tcf_ct)Systems using kernel network qdiscs/conntrack
impact

Remote Denial of Service: crafted fragmented traffic can clear tc_skb_cb, trigger WARN_ON/ panic_on_warn and crash or stall kernel packet handling.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 0d76daf2013ce1da20eab5e26bd81d983e1c18fb and < fb080b6f54835d5d4d11ce3122800e6f0f6689e6
  • affected>= ec624fe740b416fb68d536b37fb8eef46f90b5c2 and < 67d6b00a54446c008f52cf70fc0c2ad0c712f85d
  • affected>= ec624fe740b416fb68d536b37fb8eef46f90b5c2 and < 2400c4b05d58834b994500a9eec90a37db44187c
  • affected>= ec624fe740b416fb68d536b37fb8eef46f90b5c2 and < 5c3ae5f6c7c6de73ea9b6a75154fe4ed343e1bac
  • affected>= ec624fe740b416fb68d536b37fb8eef46f90b5c2 and < b3d835407846134b0d54637c0281b39bebef831d
  • affected>= ec624fe740b416fb68d536b37fb8eef46f90b5c2 and < f7f45ceb855d9ba1cba594fb3f383255f7013fad
  • affected>= ec624fe740b416fb68d536b37fb8eef46f90b5c2 and < 9092e15defbe6c7bc241c306093ca9d358a578e7
  • affected>= 5.15.13 and < 5.15.217
  • affected5.16
vendor says fixed in< 5.16, >= 5.15.217 and <= 5.15.*, >= 6.1.184 and <= 6.1.*, >= 6.6.145 and <= 6.6.*, >= 6.12.97 and <= 6.12.*, >= 6.18.40 and <= 6.18.*, >= 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