Skip to content
Networks

CVE-2026-74704

8.2
High
EPSS 0.44%Patch availableAug 25, 2026

Linux kernel sch_cake ACK filter can be triggered by malformed packets causing dmesg spam or kernel panic (DoS).

common questions

Is CVE-2026-74704 being exploited?

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

How severe is CVE-2026-74704?

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

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

What does CVE-2026-74704 affect?

CVE-2026-74704 affects Linux kernel (net/sched sch_cake qdisc), Systems using sch_cake traffic-control. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74704?

Apply kernel update with fix; block untrusted traffic; disable sch_cake ACK filter if needed.

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 sch_cake qdisc)Systems using sch_cake traffic-control
impact

Remote attacker can send crafted malformed IP packets to trigger WARN_ON leading to dmesg spam or kernel panic (DoS) if panic_on_warn enabled.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 8b7138814f29933898ecd31dfc83e35a30ee69f5 and < c1693b7844a6c06d31a565e5a494948034dfd235
  • affected>= 8b7138814f29933898ecd31dfc83e35a30ee69f5 and < a4b52612004a5639c4bfc30ba93ba414b8326e2a
  • affected>= 8b7138814f29933898ecd31dfc83e35a30ee69f5 and < ae1b2f8e21a41e7c7e75511bea0c4ccc59ec1bd3
  • affected>= 8b7138814f29933898ecd31dfc83e35a30ee69f5 and < 0c4882bff34558d8d53fb04c3e96da5c327c7dc8
  • affected>= 8b7138814f29933898ecd31dfc83e35a30ee69f5 and < 2504a76e5c0694e14e15562730e1339f2d9f9458
  • affected>= 8b7138814f29933898ecd31dfc83e35a30ee69f5 and < cd2f1d9fe8a507c2dc86ad326fe221f121c47734
  • affected>= 8b7138814f29933898ecd31dfc83e35a30ee69f5 and < a1ae353d8355407c1bea971d1c1af5e7f242bb7d
  • affected>= 8b7138814f29933898ecd31dfc83e35a30ee69f5 and < 2a33516f9ef59ad11844d4fc152f889449b5daf3
  • affected4.19
vendor says fixed in< 4.19, >= 5.10.265 and <= 5.10.*, >= 5.15.216 and <= 5.15.*, >= 6.1.183 and <= 6.1.*, >= 6.6.152 and <= 6.6.*, >= 6.12.104 and <= 6.12.*, >= 6.18.45 and <= 6.18.*, >= 7.1.9 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