CVE-2026-72041

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
Trending — 4 sources updated this week
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:

espintcp: use sk_msg_free_partial to fix partial send

sk_msg_free_partial() ensures consistency of the skmsg at every iteration, without having to manually handle uncharges and offsets. This simplifies the code, and fixes some bugs in skmsg accounting when we don't send the full contents.

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
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.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). 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: 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.

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 (8)

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

espintcp: use sk_msg_free_partial to fix partial send - kernel/git/stable/linux.git - Linux kernel stable tree

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

espintcp: use sk_msg_free_partial to fix partial send - kernel/git/stable/linux.git - Linux kernel stable tree

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

espintcp: use sk_msg_free_partial to fix partial send - kernel/git/stable/linux.git - Linux kernel stable tree

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

espintcp: use sk_msg_free_partial to fix partial send - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/54d73f18f8919735f4d04d6f43374f75756c0180
Web page

espintcp: use sk_msg_free_partial to fix partial send - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/518dcb84b997dff461800b079e5f2596389f766a
Web page

espintcp: use sk_msg_free_partial to fix partial send - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ea8c051b4bd7feec7749a980f2f70e1782b84d7
Web page

espintcp: use sk_msg_free_partial to fix partial send - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/14c0b42c8a2cd9b5361bbff45b52f69c62c6a286
Web page

espintcp: use sk_msg_free_partial to fix partial send - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/007800408002d871f5699bdb944f985896730b8f

Vendor Advisories for CVE-2026-72041(1)

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

Patch Availability(9)

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 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-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
—

Weakness Classification(1)

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

All Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 30× in last 7d / 194× 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 471 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 371 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-72041?
CVE-2026-72041 is a critical-severity vulnerability; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: espintcp: use skmsgfree_partial to fix partial send skmsgfree_partial() ensures consistency of the skmsg at every iteration, without having to manually handle uncharges and offsets. This simplifies the code, and fixes some bugs in…
When was the CVE record for CVE-2026-72041 published?
The CVE record for CVE-2026-72041 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-72041 actively exploited?
CVE-2026-72041 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72041?
CVE-2026-72041 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-72041?
A fix for CVE-2026-72041 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72041 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-72041

Explore →

Is Your Infrastructure Affected by CVE-2026-72041?

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