CVE-2026-80630

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-28. 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

Also known asEUVD-2026-67506 (ENISA EUVD) · GHSA-x458-6j5f-w8xq (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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_fq_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen

Whenever fq_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 fq_codel still has 1 packet on the queue and, thus, will mistakenly deactivate the parent's class causing issues like a recent report [1] and a wild memory access in qfq:

[ 29.371146][ T360] Oops: general protection fault, probably for non-canonical address 0xfbd59c0000000024: 0000 [#1] SMP KASAN NOPTI [ 29.371666][ T360] KASAN: maybe wild-memory-access in range [0xdead000000000120-0xdead000000000127] [ 29.371987][ T360] CPU: 6 UID: 0 PID: 360 Comm: tc Not tainted 7.1.0-rc5-00285-gc530e5b2dbc6-dirty #82 PREEMPT(full) [ 29.372384][ T360] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 [ 29.372620][ T360] 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 [ 29.373544][ T360] RSP: 0018:ffff888102417370 EFLAGS: 00010216 [ 29.373800][ T360] RAX: 0000000000000000 RBX: ffff88811224d568 RCX: dffffc0000000000 [ 29.374079][ T360] RDX: 1ffff11021fe1543 RSI: ffff88810ff0aa00 RDI: dffffc0000000000 [ 29.374368][ T360] RBP: ffff88811224c280 R08: dead000000000122 R09: 1bd5a00000000024 [ 29.374649][ T360] R10: fffffbfff7940329 R11: fffffbfff7940329 R12: 0000000000000000 [ 29.374926][ T360] R13: dead000000000100 R14: ffff88811224d580 R15: ffff88811224d578 [ 29.375207][ T360] FS: 00007f5b794e5780(0000) GS:ffff88815d1e9000(0000) knlGS:0000000000000000 [ 29.375545][ T360] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 29.375823][ T360] CR2: 000055ffb091f000 CR3: 000000010a305000 CR4: 0000000000750ef0 [ 29.376103][ T360] PKRU: 55555554 [ 29.376258][ T360] Call Trace: [ 29.376401][ T360] ... [ 29.376885][ T360] qfq_reset_qdisc (net/sched/sch_qfq.c:357 net/sched/sch_qfq.c:1487) sch_qfq [ 29.377074][ T360] qdisc_reset (net/sched/sch_generic.c:1057) [ 29.377414][ T360] __qdisc_destroy (net/sched/sch_generic.c:1096) [ 29.377600][ T360] qdisc_graft (net/sched/sch_api.c:1062 net/sched/sch_api.c:1053 net/sched/sch_api.c:1159) [ 29.378593][ T360] 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.

[1] http://lore.kernel.org/netdev/CAN2cbVe79oj0O9==m4+4x3v+O+qzRagA=2=wkrp9i9=CqYvyZA@mail.gmail.com/

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). 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 28, 2026

Last Modified

October 16, 2026

Advisory Details (8)

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

net/sched: sch_fq_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/af54df2f44d9605614bc7ed96640302a240a9a62
Web page

net/sched: sch_fq_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/acc08a0c7f37ebb1901144e03a7cba7d4afd9203
Web page

net/sched: sch_fq_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/94a5f1efdefb01f82cd228bf4e7ef1e8fc075c80
Web page

net/sched: sch_fq_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/7c09843fd2b44d9bf0de798683861d1aecd62a08
Web page

net/sched: sch_fq_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/3e515188393e62a718ccebee651ee74514104ff6
Web page

net/sched: sch_fq_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/20dd591d8f951e1e6aca5052be8785e6181055e2
Web page

net/sched: sch_fq_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/097f6fc7b1ae362dd7a9444b2572162fda73b284
Web page

net/sched: sch_fq_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/0500af8630c3253f0dde879bd3a73a06bb2f2b3f

Vendor Advisories for CVE-2026-80630(1)

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

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-11-02ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1118.115) @ jammy2026-11-02ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-11-02ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-11-02ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-11-02ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1112.112) @ jammy2026-11-02ubuntu
ubuntulinux-tools-aws-edge (7.0.0-1014.14~24.04.1) @ noble2026-11-02ubuntu
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-11-02ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-11-02ubuntu
ubuntulinux-virtual-6.8 (6.8.0-147.147) @ noble2026-11-02ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-11-02ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-38.38~24.04.4) @ noble2026-11-02ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1071.79) @ noble2026-11-02ubuntu

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

(13)

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 29× in last 7d / 153× 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 430 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 330 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-80630?
CVE-2026-80630 is a critical-severity vulnerability; its CVE record was published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_fq_codel: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen Whenever fq_codel drops packets during peek, it calls qdisc_tree_reduce_backlog. An issue arises because it calls…
When was the CVE record for CVE-2026-80630 published?
The CVE record for CVE-2026-80630 was published on August 28, 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 October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-80630 actively exploited?
CVE-2026-80630 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80630?
CVE-2026-80630 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-80630?
A fix for CVE-2026-80630 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80630 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-80630

Explore →

Is Your Infrastructure Affected by CVE-2026-80630?

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

Book a Demo →Browse All CVEs