CVE-2026-72036

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.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_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked

multiq_dequeue() takes a packet from a band's child with a direct ->dequeue() call after multiq_peek() peeked it. When the child is non-work-conserving the peek stashes the skb in the child's gso_skb, so the direct dequeue returns a different skb and orphans the stash, desyncing the child's qlen/backlog. With a qfq child reached through a peeking parent (e.g. tbf) this re-enters the child on an emptied list and dereferences NULL, panicking the kernel from softirq on ordinary egress.

Take the packet through qdisc_dequeue_peeked(), as sch_prio already does and as sch_red and sch_sfb were just fixed to do. The helper is a no-op when the child has no stash, so a work-conserving child is unaffected.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
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_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86a61e46a1919e8abf4d227c204773dabb24068a
generic

net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5889064919a1e5c0a9469c54895000414fc46944
generic

net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/54f6b0c843e228d499eb4b6bbb89df68cad9ad5d
generic

net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e5fd9d14f2d228e7260251f2e4a1d41ba8f705a
generic

net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b9cc255e8089606b92b2adf504e334573682821

Vendor Advisories for CVE-2026-72036(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 31× in last 7d / 31× 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-20 23:45 UTCEG score recompute
  2. 2026-08-20 23:45 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 11:00 UTCGHSA enrichment
  5. 2026-08-19 22:14 UTCEG score recompute
  6. 2026-08-19 22:14 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 09:28 UTCGHSA enrichment
  9. 2026-08-18 20:40 UTCEG score recompute
  10. 2026-08-18 20:40 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 07:54 UTCGHSA enrichment
  14. 2026-08-17 19:09 UTCEG score recompute
  15. 2026-08-17 19:08 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 06:22 UTCEG score recompute
  18. 2026-08-17 06:22 UTCGHSA enrichment
  19. 2026-08-17 06:01 UTCEG score recompute▲ 7.80
  20. 2026-08-17 06:01 UTCGHSA enrichment
  21. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  22. 2026-08-17 05:34 UTCEG score recompute
  23. 2026-08-17 05:34 UTCGHSA enrichment
  24. 2026-08-17 05:24 UTCMITRE cvelistV5
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 6 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 02:15 UTCEPSS rescore
  3. 2026-08-15 06:45 UTCGHSA enrichment
  4. 2026-08-15 06:23 UTCNVD update
  5. 2026-08-15 06:19 UTCEG score recompute
  6. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72036?
CVE-2026-72036 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: net/sched: schmultiq: Replace direct dequeue call with peek and qdiscdequeue_peeked multiq_dequeue() takes a packet from a band's child with a direct ->dequeue() call after multiq_peek() peeked it. When the child is…
When was CVE-2026-72036 disclosed?
CVE-2026-72036 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-72036 actively exploited?
CVE-2026-72036 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.9% of all scored CVEs.
What is the CVSS score of CVE-2026-72036?
CVE-2026-72036 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72036?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72036, 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-72036

Explore →

Is Your Infrastructure Affected by CVE-2026-72036?

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

Start Free Scan →Browse All CVEs