CVE-2026-93105

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

esp: do not unref managed frag pages in esp_ssg_unref()

esp_ssg_unref() releases the page references held on the source scatterlist after the AEAD operation completes. It calls skb_page_unref() on every frag page for an out-of-place transform (req->src != req->dst), and in the error path of esp_output_tail() (already_unref == true) on the request's own scatterlist.

This is wrong when the skb carries managed frags (SKBFL_MANAGED_FRAG_REFS). Managed frags are owned by a zerocopy ubuf and the skb does not hold a per-frag page reference; io_uring SEND_ZC with a registered buffer attaches the bvec pages this way via io_sg_from_iter(). The rest of the stack honours this invariant: skb_release_data() skips the per-frag unref when SKBFL_MANAGED_FRAG_REFS is set, and skb_zcopy_managed() is the guard used at the other unref sites.

esp_ssg_unref() is missing that guard, so for a managed-frag skb it drops a page reference the skb never acquired. This can underflow the page reference count and free a page that is still in use.

Guard the function with skb_zcopy_managed() so both unref paths are skipped for managed-frag skbs, matching skb_release_data().

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

esp: do not unref managed frag pages in esp_ssg_unref() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26b6b14c7a0368e317a1e9fb5144ebe6f8d495cf
generic

esp: do not unref managed frag pages in esp_ssg_unref() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21697720ff43b8dfa25b8e8d9ca7f56f4597fc80

Vendor Advisories for CVE-2026-93105(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 36× in last 7d / 96× 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-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 22:46 UTCGHSA enrichment
  3. 2026-10-04 09:52 UTCVendor advisory
  4. 2026-10-04 09:52 UTCGHSA enrichment
  5. 2026-10-03 20:58 UTCEG score recompute
  6. 2026-10-03 20:58 UTCVendor advisory
  7. 2026-10-03 20:58 UTCGHSA enrichment
  8. 2026-10-03 08:04 UTCVendor advisory
  9. 2026-10-03 08:04 UTCGHSA enrichment
  10. 2026-10-02 18:53 UTCEG score recompute
  11. 2026-10-02 18:53 UTCVendor advisory
  12. 2026-10-02 18:53 UTCGHSA enrichment
  13. 2026-10-02 05:59 UTCEG score recompute
  14. 2026-10-02 05:59 UTCVendor advisory
  15. 2026-10-02 05:59 UTCGHSA enrichment
  16. 2026-10-01 19:51 UTCEPSS rescore
  17. 2026-10-01 17:05 UTCVendor advisory
  18. 2026-10-01 17:05 UTCGHSA enrichment
  19. 2026-10-01 03:33 UTCEG score recompute
  20. 2026-10-01 03:33 UTCVendor advisory
  21. 2026-10-01 03:33 UTCGHSA enrichment
  22. 2026-09-30 15:04 UTCEPSS rescore
  23. 2026-09-30 14:39 UTCVendor advisory
  24. 2026-09-30 14:39 UTCGHSA enrichment
  25. 2026-09-30 01:42 UTCEG score recompute
Show 71 more
  1. 2026-09-30 01:42 UTCVendor advisory
  2. 2026-09-30 01:42 UTCGHSA enrichment
  3. 2026-09-29 12:48 UTCVendor advisory
  4. 2026-09-29 12:48 UTCGHSA enrichment
  5. 2026-09-28 23:54 UTCEG score recompute
  6. 2026-09-28 23:54 UTCVendor advisory
  7. 2026-09-28 23:54 UTCGHSA enrichment
  8. 2026-09-28 13:52 UTCEPSS rescore
  9. 2026-09-28 13:52 UTCEPSS rescore
  10. 2026-09-28 11:00 UTCVendor advisory
  11. 2026-09-28 11:00 UTCGHSA enrichment
  12. 2026-09-27 22:05 UTCEG score recompute
  13. 2026-09-27 22:05 UTCVendor advisory
  14. 2026-09-27 22:05 UTCGHSA enrichment
  15. 2026-09-27 13:49 UTCEPSS rescore
  16. 2026-09-27 09:09 UTCVendor advisory
  17. 2026-09-27 09:09 UTCGHSA enrichment
  18. 2026-09-26 20:11 UTCEG score recompute
  19. 2026-09-26 20:11 UTCVendor advisory
  20. 2026-09-26 20:11 UTCGHSA enrichment
  21. 2026-09-26 15:59 UTCEPSS rescore
  22. 2026-09-26 07:16 UTCEG score recompute
  23. 2026-09-26 07:16 UTCVendor advisory
  24. 2026-09-26 07:16 UTCGHSA enrichment
  25. 2026-09-25 18:22 UTCVendor advisory
  26. 2026-09-25 18:22 UTCGHSA enrichment
  27. 2026-09-25 05:19 UTCVendor advisory
  28. 2026-09-25 05:19 UTCGHSA enrichment
  29. 2026-09-24 16:25 UTCEG score recompute
  30. 2026-09-24 16:25 UTCVendor advisory
  31. 2026-09-24 16:25 UTCGHSA enrichment
  32. 2026-09-24 14:04 UTCEPSS rescore
  33. 2026-09-24 03:31 UTCEG score recompute
  34. 2026-09-24 03:31 UTCVendor advisory
  35. 2026-09-24 03:31 UTCGHSA enrichment
  36. 2026-09-23 17:54 UTCEPSS rescore
  37. 2026-09-23 14:37 UTCVendor advisory
  38. 2026-09-23 14:37 UTCGHSA enrichment
  39. 2026-09-23 01:41 UTCEG score recompute
  40. 2026-09-23 01:41 UTCVendor advisory
  41. 2026-09-23 01:41 UTCGHSA enrichment
  42. 2026-09-22 16:01 UTCEPSS rescore
  43. 2026-09-22 12:46 UTCVendor advisory
  44. 2026-09-22 12:46 UTCGHSA enrichment
  45. 2026-09-21 23:52 UTCEG score recompute
  46. 2026-09-21 23:52 UTCVendor advisory
  47. 2026-09-21 23:52 UTCGHSA enrichment
  48. 2026-09-21 21:09 UTCEPSS rescore
  49. 2026-09-21 10:58 UTCVendor advisory
  50. 2026-09-21 10:58 UTCGHSA enrichment
  51. 2026-09-20 22:04 UTCEG score recompute
  52. 2026-09-20 22:04 UTCVendor advisory
  53. 2026-09-20 22:04 UTCGHSA enrichment
  54. 2026-09-20 20:16 UTCEPSS rescore
  55. 2026-09-20 09:10 UTCVendor advisory
  56. 2026-09-20 09:10 UTCGHSA enrichment
  57. 2026-09-19 20:15 UTCEG score recompute
  58. 2026-09-19 20:15 UTCVendor advisory
  59. 2026-09-19 20:15 UTCGHSA enrichment
  60. 2026-09-19 07:20 UTCEG score recompute
  61. 2026-09-19 07:20 UTCVendor advisory
  62. 2026-09-19 07:20 UTCGHSA enrichment
  63. 2026-09-18 19:28 UTCEPSS rescore
  64. 2026-09-18 18:26 UTCEG score recompute
  65. 2026-09-18 18:26 UTCGHSA enrichment
  66. 2026-09-18 18:00 UTCEG score recompute▲ 7.80
  67. 2026-09-18 18:00 UTCGHSA enrichment
  68. 2026-09-18 17:59 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  69. 2026-09-17 17:24 UTCNVD update
  70. 2026-09-17 16:21 UTCEG score recompute
  71. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93105?
CVE-2026-93105 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: esp: do not unref managed frag pages in espssgunref() espssgunref() releases the page references held on the source scatterlist after the AEAD operation completes. It calls skbpageunref() on every frag page for an out-of-place…
When was CVE-2026-93105 disclosed?
CVE-2026-93105 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93105 actively exploited?
CVE-2026-93105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93105?
CVE-2026-93105 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93105?
No fix for CVE-2026-93105 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-93105 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-93105

Explore →

Is Your Infrastructure Affected by CVE-2026-93105?

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

Book a Demo →Browse All CVEs