CVE-2026-23239

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-10. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

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

espintcp: Fix race condition in espintcp_close()

This issue was discovered during a code audit.

After cancel_work_sync() is called from espintcp_close(), espintcp_tx_work() can still be scheduled from paths such as the Delayed ACK handler or ksoftirqd. As a result, the espintcp_tx_work() worker may dereference a freed espintcp ctx or sk.

The following is a simple race scenario:

cpu0 cpu1

espintcp_close() cancel_work_sync(&ctx->work); espintcp_write_space() schedule_work(&ctx->work);

To prevent this race condition, cancel_work_sync() is replaced with disable_work_sync().

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

March 10, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

espintcp: Fix race condition in espintcp_close() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f7ad8b1d0e421c524604d5076b73232093490d5c
generic

espintcp: Fix race condition in espintcp_close() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e1512c1db9e8794d8d130addd2615ec27231d994
generic

espintcp: Fix race condition in espintcp_close() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/664e9df53226b4505a0894817ecad2c610ab11d8
generic

espintcp: Fix race condition in espintcp_close() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/022ff7f347588de6e17879a1da6019647b21321b

Vendor Advisories for CVE-2026-23239(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.75osv

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 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (113 versions)6.19.6-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 44× 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.

Showing the most recent 100 of 180 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23239?
CVE-2026-23239 is a high vulnerability published on March 10, 2026. In the Linux kernel, the following vulnerability has been resolved: espintcp: Fix race condition in espintcp_close() This issue was discovered during a code audit. After cancelworksync() is called from espintcp_close(), espintcptxwork() can still be scheduled from paths such as the Delayed ACK…
When was CVE-2026-23239 disclosed?
CVE-2026-23239 was first published in the National Vulnerability Database on March 10, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23239 actively exploited?
CVE-2026-23239 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.0% of all scored CVEs.
What is the CVSS score of CVE-2026-23239?
CVE-2026-23239 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23239?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23239, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23239

Explore →

Is Your Infrastructure Affected by CVE-2026-23239?

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