CVE-2026-74267

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen

Whenever codel drops packets during peek, it calls qdisc_tree_reduce_backlog. An issue arises because it calls qdisc_tree_reduce_backlog before it reincrements the qlen. If qlen drops to zero, but peek returns an skb, the parent's qlen_notify callback will be executed even though codel still has 1 packet on the queue and, thus, will mistakenly deactivate the parent's class causing issues like a wild memory access when qfq has codel as a child:

[ 36.339843][ T370] Oops: general protection fault, probably for non-canonical address 0xfbd59c0000000024: 0000 [#1] SMP KASAN NOPTI [ 36.340408][ T370] KASAN: maybe wild-memory-access in range [0xdead000000000120-0xdead000000000127] [ 36.340737][ T370] CPU: 2 UID: 0 PID: 370 Comm: tc Not tainted 7.1.0-rc5-00287-g66e13b626592 #87 PREEMPT(full) [ 36.341113][ T370] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 [ 36.341357][ T370] RIP: 0010:qfq_deactivate_agg (include/linux/list.h:1029 (discriminator 2) include/linux/list.h:1043 (discriminator 2) net/sched/sch_qfq.c:1369 (discriminator 2) net/sched/sch_qfq.c:1395 (discriminator 2)) sch_qfq [ 36.342221][ T370] RSP: 0018:ffff8881100ef370 EFLAGS: 00010216 [ 36.342422][ T370] RAX: 0000000000000000 RBX: ffff8881058a9568 RCX: dffffc0000000000 [ 36.342664][ T370] RDX: 1ffff11021064dc3 RSI: ffff888108326e00 RDI: dffffc0000000000 [ 36.342905][ T370] RBP: ffff8881058a8280 R08: dead000000000122 R09: 1bd5a00000000024 [ 36.343140][ T370] R10: fffffbfff2940329 R11: fffffbfff2940329 R12: 0000000000000000 [ 36.343383][ T370] R13: dead000000000100 R14: ffff8881058a9580 R15: ffff8881058a9578 [ 36.343631][ T370] FS: 00007fc04b0ca780(0000) GS:ffff888184fef000(0000) knlGS:0000000000000000 [ 36.343911][ T370] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 36.344116][ T370] CR2: 0000557c02c02000 CR3: 000000010e0ba000 CR4: 0000000000750ef0 [ 36.344359][ T370] PKRU: 55555554 [ 36.344481][ T370] Call Trace: ... [ 36.345054][ T370] qfq_reset_qdisc (net/sched/sch_qfq.c:357 net/sched/sch_qfq.c:1487) sch_qfq [ 36.345222][ T370] qdisc_reset (net/sched/sch_generic.c:1057) [ 36.345503][ T370] __qdisc_destroy (net/sched/sch_generic.c:1096) [ 36.345677][ T370] qdisc_graft (net/sched/sch_api.c:1062 net/sched/sch_api.c:1053 net/sched/sch_api.c:1159) [ 36.346335][ T370] tc_get_qdisc (net/sched/sch_api.c:1528 net/sched/sch_api.c:1556)

Fix this by only calling qdisc_tree_reduce_backlog in peek after the qlen is restored.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eba49fd85995a3851c597fa2d214f8d21736e1d8
generic

net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e8c6dbadf139cb14ea6ed14add6ed6e88504dedd
generic

net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e4615aa6bb7802944ae790cb4b3ef8c1b7491af3
generic

net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bb9cfd874ee884117b33e92a002b9a45b48202f4
generic

net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91e0a793a72374c20ab31a40ccec21373e82e973
generic

net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7a05af7f58566682b73578b72ca8e53a268c43bd
generic

net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/755108bb7a5083e911294c416cfea605dc75632f
generic

net/sched: sch_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52f1da34c9f4d5bdc1e8b44242da5c7ba8db85f3

Vendor Advisories for CVE-2026-74267(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 46× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 07:41 UTCGHSA enrichment
  2. 2026-08-21 03:17 UTCEG score recompute
  3. 2026-08-21 03:17 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 22:50 UTCGHSA enrichment
  6. 2026-08-20 18:26 UTCGHSA enrichment
  7. 2026-08-20 14:03 UTCGHSA enrichment
  8. 2026-08-20 09:39 UTCGHSA enrichment
  9. 2026-08-20 05:16 UTCGHSA enrichment
  10. 2026-08-20 00:51 UTCGHSA enrichment
  11. 2026-08-19 20:24 UTCEG score recompute
  12. 2026-08-19 20:24 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-19 15:56 UTCGHSA enrichment
  15. 2026-08-19 11:31 UTCGHSA enrichment
  16. 2026-08-19 07:06 UTCGHSA enrichment
  17. 2026-08-19 02:42 UTCGHSA enrichment
  18. 2026-08-18 22:14 UTCGHSA enrichment
  19. 2026-08-18 17:49 UTCEG score recompute
  20. 2026-08-18 17:49 UTCGHSA enrichment
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 13:10 UTCGHSA enrichment
  24. 2026-08-18 08:45 UTCGHSA enrichment
  25. 2026-08-18 04:22 UTCGHSA enrichment
Show 21 more
  1. 2026-08-17 23:58 UTCGHSA enrichment
  2. 2026-08-17 19:34 UTCGHSA enrichment
  3. 2026-08-17 15:10 UTCEG score recompute
  4. 2026-08-17 15:10 UTCGHSA enrichment
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-17 10:46 UTCEG score recompute
  7. 2026-08-17 10:46 UTCGHSA enrichment
  8. 2026-08-17 06:23 UTCEG score recompute
  9. 2026-08-17 06:23 UTCGHSA enrichment
  10. 2026-08-17 05:56 UTCEG score recompute▲ 9.80
  11. 2026-08-17 05:56 UTCGHSA enrichment
  12. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  13. 2026-08-17 05:27 UTCEG score recompute
  14. 2026-08-17 05:27 UTCGHSA enrichment
  15. 2026-08-17 05:24 UTCMITRE cvelistV5
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:15 UTCEPSS rescore
  19. 2026-08-15 06:23 UTCNVD update
  20. 2026-08-15 06:17 UTCEG score recompute
  21. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74267?
CVE-2026-74267 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: net/sched: schcodel: Do not call qdisctreereducebacklog during peek before restoring qlen Whenever codel drops packets during peek, it calls qdisctreereduce_backlog. An issue arises because it calls qdisctreereduce_backlog before…
When was CVE-2026-74267 disclosed?
CVE-2026-74267 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74267 actively exploited?
CVE-2026-74267 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 49.4% of all scored CVEs.
What is the CVSS score of CVE-2026-74267?
CVE-2026-74267 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-74267?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74267, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74267

Explore →

Is Your Infrastructure Affected by CVE-2026-74267?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs