CVE-2026-23240

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.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: 9.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:

tls: Fix race condition in tls_sw_cancel_work_tx()

This issue was discovered during a code audit.

After cancel_delayed_work_sync() is called from tls_sk_proto_close(), tx_work_handler() can still be scheduled from paths such as the Delayed ACK handler or ksoftirqd. As a result, the tx_work_handler() worker may dereference a freed TLS object.

The following is a simple race scenario:

cpu0 cpu1

tls_sk_proto_close() tls_sw_cancel_work_tx() tls_write_space() tls_sw_write_space() if (!test_and_set_bit(BIT_TX_SCHEDULED, &tx_ctx->tx_bitmask)) set_bit(BIT_TX_SCHEDULED, &ctx->tx_bitmask); cancel_delayed_work_sync(&ctx->tx_work.work); schedule_delayed_work(&tx_ctx->tx_work.work, 0);

To prevent this race condition, cancel_delayed_work_sync() is replaced with disable_delayed_work_sync().

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
41%
KEV
Not listed

Published

March 10, 2026

Last Modified

August 5, 2026

Advisory Details (4)

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

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

https://git.kernel.org/stable/c/7bb09315f93dce6acc54bf59e5a95ba7365c2be4
generic

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

https://git.kernel.org/stable/c/17153f154f80be2b47ebf52840f2d8f724eb2f3b
generic

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

https://git.kernel.org/stable/c/854cd32bc74fe573353095e90958490e4e4d641b
generic

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

https://git.kernel.org/stable/c/a5de36d6cee74a92c1a21b260bc507e64bc451de

Vendor Advisories for CVE-2026-23240(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.75—osv

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~rc7-1~exp1 (350 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 (116 versions)6.19.6-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 24× 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 232 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-23240?
CVE-2026-23240 is a critical vulnerability published on March 10, 2026. In the Linux kernel, the following vulnerability has been resolved: tls: Fix race condition in tlsswcancelworktx() This issue was discovered during a code audit. After canceldelayedworksync() is called from tlsskprotoclose(), txworkhandler() can still be scheduled from paths such as the Delayed ACK…
When was CVE-2026-23240 disclosed?
CVE-2026-23240 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-23240 actively exploited?
CVE-2026-23240 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 58.8% of all scored CVEs.
What is the CVSS score of CVE-2026-23240?
CVE-2026-23240 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-23240?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23240, 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-23240

Explore →

Is Your Infrastructure Affected by CVE-2026-23240?

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

Start Free Scan →Browse All CVEs