CVE-2026-72035
Linux kernel taprio qdisc bug can cause kernel panic on egress (DoS)
Is CVE-2026-72035 being exploited?
Not confirmed. CVE-2026-72035 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.57% probability of exploitation in the next 30 days.
How severe is CVE-2026-72035?
CVE-2026-72035 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-72035?
Yes. A fix has been recorded for CVE-2026-72035. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72035 affect?
CVE-2026-72035 affects Linux kernel (sch_taprio qdisc), Systems using taprio/time-aware shapers, Networked Linux hosts/routers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72035?
Apply kernel updates with the sch_taprio fix and reboot affected hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted egress traffic via sch_taprio can trigger NULL deref and kernel panic in softirq, causing denial of service (system crash).
Patch when possible
- affected>= 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 and < 51f8af240aed903e988755af33d7491030b50ae9
- affected>= 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 and < 17ab5f76f3899f67e5569722f334591f4b88b17b
- affected>= 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 and < f60d5c12e0551012cee5c272b0bcbcc78f7bb506
- affected>= 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 and < 6ee5a7665a9080bcb05d703bf981a579436fd05e
- affected>= 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 and < 18d580cb00c55805633bae45e90cf22ed6b8e424
- affected>= 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 and < e2b7ee61989f2d39df6c2cc06f9db1aea69bdb09
- affected>= 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 and < 2dcebbd1ad2e180fe7b98bf346ced69a872e11e6
- affected>= 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22 and < e056e1dfcddca877dd46d704e8ec9860cfc9ec44
- 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.