CVE-2026-80609

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
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.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

qede: fix out-of-bounds check for cqe->len_list[]

Move index check before element access.

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.7% × 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.7%
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 28, 2026

Last Modified

August 29, 2026

Advisory Details (7)

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

qede: fix out-of-bounds check for cqe->len_list[] - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f9ba47fce5932c15891c89c60e76dfaca919cb8d
Web page

qede: fix out-of-bounds check for cqe->len_list[] - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e30af53dca803893a29eb3bbe0539752ba435410
Web page

qede: fix out-of-bounds check for cqe->len_list[] - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bd3a6a083b408e96437dbd86ff543ba9ec3a788b
Web page

qede: fix out-of-bounds check for cqe->len_list[] - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b17751a2ebc4aef3ce6be6f71ee8df92bf5ddfcd
Web page

qede: fix out-of-bounds check for cqe->len_list[] - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6d46ab395803f162cdc50e8d346e5f1a4e766771
Web page

qede: fix out-of-bounds check for cqe->len_list[] - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6d203bdd227fca1787f8a80cf84b990936633c5a
Web page

qede: fix out-of-bounds check for cqe->len_list[] - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-80609(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-aws-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-14ubuntu
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-10-14ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-10-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-38.38~24.04.4) @ noble2026-10-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1112.112) @ jammy2026-10-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-10-14ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-10-14ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-14ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-10-14ubuntu
ubuntulinux-virtual-6.8 (6.8.0-147.147) @ noble2026-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-tools-gcp-lts-22.04 (5.15.0.1118.115) @ jammy2026-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

(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 38× in last 7d / 211× 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 99 of 344 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 245 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-80609?
CVE-2026-80609 is a critical-severity vulnerability; its CVE record was published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: qede: fix out-of-bounds check for cqe->len_list[] Move index check before element access.
When was the CVE record for CVE-2026-80609 published?
The CVE record for CVE-2026-80609 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 August 29, 2026; the record at its source may have been updated since.
Is CVE-2026-80609 actively exploited?
CVE-2026-80609 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80609?
CVE-2026-80609 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-80609?
A fix for CVE-2026-80609 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80609 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-80609

Explore →

Is Your Infrastructure Affected by CVE-2026-80609?

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

Book a Demo →Browse All CVEs