CVE-2026-74284

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: 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_hfsc: Don't make class passive twice

update_vf() is called from two places for the same class during a single dequeue when the class's child qdisc (e.g. codel/fq_codel) drops its last packets while dequeuing:

  • The child calls qdisc_tree_reduce_backlog(), which, now that the child
is empty, invokes hfsc_qlen_notify() -> update_vf(cl, 0, 0) and turns the class passive (cl_nactive is decremented up the hierarchy).
  • hfsc_dequeue() then calls update_vf(cl, qdisc_pkt_len(skb), cur_time)
to charge the dequeued bytes.

On the second call the class is already passive, but its child qdisc is still empty, so update_vf() arms go_passive again:

if (cl->qdisc->q.qlen == 0 && cl->cl_flags & HFSC_FSC) go_passive = 1;

The leaf is then skipped by the cl_nactive == 0 check inside the loop, which does not clear go_passive, so the stale go_passive propagates to the parent and decrements its cl_nactive a second time. A parent that still has other active children is driven to cl_nactive == 0 and removed from the vttree, even though those siblings are still backlogged. They are never dequeued again and the qdisc stalls.

Fix this by only arming go_passive when the class is actually active, so an already-passive class no longer triggers a second passive transition. The byte accounting (cl->cl_total += len) still runs for every ancestor, so dequeued bytes continue to be counted exactly once.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Vendor Advisories for CVE-2026-74284(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 17× in last 7d / 17× 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 22:56 UTCEPSS rescore
  2. 2026-08-20 12:29 UTCGHSA enrichment
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-18 13:49 UTCEPSS rescore
  5. 2026-08-18 13:49 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 06:22 UTCGHSA enrichment
  8. 2026-08-17 06:22 UTCNVD update
  9. 2026-08-17 05:27 UTCEG score recompute
  10. 2026-08-17 05:27 UTCGHSA enrichment
  11. 2026-08-17 05:24 UTCMITRE cvelistV5
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 02:15 UTCEPSS rescore
  15. 2026-08-15 06:23 UTCNVD update
  16. 2026-08-15 06:17 UTCEG score recompute
  17. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-74284?
CVE-2026-74284 is a publicly disclosed vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_hfsc: Don't make class passive twice update_vf() is called from two places for the same class during a single dequeue when the class's child qdisc (e.g. codel/fq_codel) drops its last packets while dequeuing: 1. The…
When was CVE-2026-74284 disclosed?
CVE-2026-74284 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-74284 actively exploited?
CVE-2026-74284 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 88.4% of all scored CVEs.
How do I remediate CVE-2026-74284?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74284, 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-74284

Explore →

Is Your Infrastructure Affected by CVE-2026-74284?

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