CVE-2026-74267

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.8%
EPSS %ILE
53rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Oct 13, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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.

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1122.131) @ jammy2026-10-14ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-14ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1012.12~24.04.1) @ noble2026-10-14ubuntu
ubuntulinux-tools-gke-hwe-26.04 (7.0.0-1007.8) @ resolute2026-10-14ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-10-14ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1118.115) @ jammy2026-10-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1014.14) @ resolute2026-10-14ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-34.34) @ resolute2026-10-14ubuntu
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-10-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1112.112) @ jammy2026-10-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1071.79) @ noble2026-10-14ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-10-14ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-10-14ubuntu
ubuntulinux-virtual-6.8 (6.8.0-147.147) @ noble2026-10-14ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(15)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 17× in last 7d / 210× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 418 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 318 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 09:00 UTCEG score recompute
  2. 2026-10-14 09:00 UTCVendor advisory
  3. 2026-10-14 08:59 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  5. 2026-10-13 05:37 UTCEG score recompute
  6. 2026-10-13 05:37 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  8. 2026-10-12 15:40 UTCEG score recompute
  9. 2026-10-12 05:40 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-11 19:26 UTCEG score recompute
  11. 2026-10-11 16:41 UTCEG score recompute
  12. 2026-10-11 14:00 UTCEG score recompute
  13. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  14. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  15. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  18. 2026-10-07 07:26 UTCVendor advisory
  19. 2026-10-07 07:26 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-07 02:56 UTCVendor advisory
  21. 2026-10-07 02:56 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-06 22:32 UTCVendor advisory
  23. 2026-10-06 22:32 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-06 18:00 UTCEG score recompute
  25. 2026-10-06 18:00 UTCVendor advisory
Show 75 more
  1. 2026-10-06 18:00 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  3. 2026-10-06 13:36 UTCVendor advisory
  4. 2026-10-06 13:36 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-06 09:12 UTCEG score recompute
  6. 2026-10-06 09:12 UTCVendor advisory
  7. 2026-10-06 09:12 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  9. 2026-10-05 17:34 UTCVendor advisory
  10. 2026-10-05 17:34 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-05 12:16 UTCVendor advisory
  12. 2026-10-05 12:16 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-05 06:49 UTCVendor advisory
  14. 2026-10-05 06:49 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-05 06:48 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-05 02:24 UTCEG score recompute
  17. 2026-10-05 02:24 UTCVendor advisory
  18. 2026-10-05 02:24 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  20. 2026-10-04 21:58 UTCVendor advisory
  21. 2026-10-04 21:58 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-04 12:32 UTCVendor advisory
  23. 2026-10-04 12:32 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-04 08:08 UTCVendor advisory
  25. 2026-10-04 08:08 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-04 03:31 UTCVendor advisory
  27. 2026-10-04 03:31 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-03 19:32 UTCEG score recompute
  29. 2026-10-03 19:32 UTCVendor advisory
  30. 2026-10-03 19:32 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  32. 2026-10-03 02:10 UTCVendor advisory
  33. 2026-10-03 02:10 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-02 21:46 UTCEG score recompute
  35. 2026-10-02 21:46 UTCVendor advisory
  36. 2026-10-02 21:46 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-02 15:52 UTCVendor advisory
  38. 2026-10-02 15:52 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-02 07:06 UTCEG score recompute
  40. 2026-10-02 07:06 UTCVendor advisory
  41. 2026-10-02 07:05 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  43. 2026-10-01 14:45 UTCVendor advisory
  44. 2026-10-01 14:45 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-01 10:21 UTCVendor advisory
  46. 2026-10-01 10:21 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-01 05:57 UTCVendor advisory
  48. 2026-10-01 05:57 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-01 01:34 UTCVendor advisory
  50. 2026-10-01 01:34 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-09-30 21:01 UTCEG score recompute
  52. 2026-09-30 21:01 UTCVendor advisory
  53. 2026-09-30 21:00 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  55. 2026-09-29 04:27 UTCVendor advisory
  56. 2026-09-29 04:27 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-09-29 00:03 UTCEG score recompute
  58. 2026-09-29 00:03 UTCVendor advisory
  59. 2026-09-29 00:02 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  61. 2026-09-28 12:00 UTCVendor advisory
  62. 2026-09-28 12:00 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-09-28 07:36 UTCVendor advisory
  64. 2026-09-28 07:36 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-09-28 03:12 UTCVendor advisory
  66. 2026-09-28 03:12 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-09-27 22:48 UTCVendor advisory
  68. 2026-09-27 22:48 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-09-27 17:25 UTCEG score recompute
  70. 2026-09-27 17:25 UTCVendor advisory
  71. 2026-09-27 17:25 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  73. 2026-09-27 12:57 UTCVendor advisory
  74. 2026-09-27 12:57 UTCGHSA enrichmentGHSA-f72g-gj5h-9p7f · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-09-27 08:29 UTCEG score recompute

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-74267?
CVE-2026-74267 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-74267 published?
The CVE record for CVE-2026-74267 was published on August 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 17, 2026; the record at its source may have been updated since.
Is CVE-2026-74267 actively exploited?
CVE-2026-74267 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74267?
CVE-2026-74267 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74267?
A fix for CVE-2026-74267 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74267 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs