CVE-2026-72065

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

Also known asEUVD-2026-59023 (ENISA EUVD) · GHSA-pwf3-8jwg-55rq (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.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:

net: mana: Validate the packet length reported by the NIC

Validate the packet length reported in the RX CQE before passing it to skb processing. The CQE is supplied by the NIC device and should not be blindly trusted.

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.7% × 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.7%
EPSS %ILE
54th
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.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 15, 2026

Last Modified

October 19, 2026

Advisory Details (7)

Auto-updated Nov 7, 2026
Patch available.
Web page

net: mana: Validate the packet length reported by the NIC - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mana: Validate the packet length reported by the NIC - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mana: Validate the packet length reported by the NIC - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: mana: Validate the packet length reported by the NIC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6080189291d958604dcefe513a13900835ac982f
Web page

net: mana: Validate the packet length reported by the NIC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e2a83b4998af4384e677d3b2ac08565274279bf
Web page

net: mana: Validate the packet length reported by the NIC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e276b14b6d378372bf0152df89286cbe7632fb0
Web page

net: mana: Validate the packet length reported by the NIC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/282c5214ca4eb3799158c76782646e86d2945d1b

Vendor Advisories for CVE-2026-72065(1)

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

Patch Availability(12)

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

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1
  • every version up to 6.12.101-1~deb12u1: fixed in 6.12.101-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)
  • every version up to 6.12.101-1: fixed in 6.12.101-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (161 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 16× in last 7d / 82× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 564 rows 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 464 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-72065?
CVE-2026-72065 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: mana: Validate the packet length reported by the NIC Validate the packet length reported in the RX CQE before passing it to skb processing. The CQE is supplied by the NIC device and should not be blindly trusted.
When was the CVE record for CVE-2026-72065 published?
The CVE record for CVE-2026-72065 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-72065 actively exploited?
CVE-2026-72065 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72065?
CVE-2026-72065 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-72065?
A fix for CVE-2026-72065 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72065 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-72065

Explore →

Is Your Infrastructure Affected by CVE-2026-72065?

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