CVE-2024-58239

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-08-22. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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

tls: stop recv() if initial process_rx_list gave us non-DATA

If we have a non-DATA record on the rx_list and another record of the same type still on the queue, we will end up merging them:

  • process_rx_list copies the non-DATA record
  • we start the loop and process the first available record since it's
of the same type
  • we break out of the loop since the record was not DATA

Just check the record type and jump to the end in case process_rx_list did some work.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/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
Severity55% × 45%
Exploitation40% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
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.3%
EPSS %ILE
26th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or 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 public PoC (EG-KEV: elevated) · 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

August 22, 2025

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Aug 5, 2026
Patch available.
generic

tls: stop recv() if initial process_rx_list gave us non-DATA - kernel/git/stable/linux.git - Linux kernel stable tree

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

tls: stop recv() if initial process_rx_list gave us non-DATA - kernel/git/stable/linux.git - Linux kernel stable tree

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

tls: stop recv() if initial process_rx_list gave us non-DATA - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b952d8fdfcf6fd8ea0b8954bc9277642cf0977f
generic

tls: stop recv() if initial process_rx_list gave us non-DATA - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6756168add1c6c3ef1c32c335bb843a5d1f99a75
generic

tls: stop recv() if initial process_rx_list gave us non-DATA - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4338032aa90bd1d5b33a4274e8fa8347cda5ee09
generic

tls: stop recv() if initial process_rx_list gave us non-DATA - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31e10d6cb0c9532ff070cf50da1657c3acee9276
generic

tls: stop recv() if initial process_rx_list gave us non-DATA - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2024-58239(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
linuxKernel @ 5.4.270 (fixes >=5.1.0)—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 rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (39 versions)
  • every version up to 5.10.216-1: fixed in 5.10.216-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.76-1~bpo11+1 (18 versions)
  • every version up to 6.1.82-1: fixed in 6.1.82-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.7-1: fixed in 6.7.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.7-1: fixed in 6.7.7-1
—

Data Freshness Timeline

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

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCkhoatran107/cve-2025-39682
    First seen Oct 14, 2025

    A variant of CVE-2024-58239

    Open source ↗
  • GitHub PoCkhoatran107/cve-2024-58239
    First seen Sep 17, 2025
    Open source ↗

Frequently asked(5)

What is CVE-2024-58239?
CVE-2024-58239 is a medium vulnerability published on August 22, 2025. In the Linux kernel, the following vulnerability has been resolved: tls: stop recv() if initial processrxlist gave us non-DATA If we have a non-DATA record on the rx_list and another record of the same type still on the queue, we will end up merging them: processrxlist copies the non-DATA record we…
When was CVE-2024-58239 disclosed?
CVE-2024-58239 was first published on August 22, 2025, 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-2024-58239 actively exploited?
CVE-2024-58239 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-58239?
CVE-2024-58239 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-58239?
A fix for CVE-2024-58239 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-58239 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-2024-58239

Explore →

Is Your Infrastructure Affected by CVE-2024-58239?

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