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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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)
EPSS
1.1%
KEV
Not listed

Published

March 10, 2026

Last Modified

May 20, 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 39× 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 108 total refreshes for this CVE.

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

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 May 20, 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 1.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.