Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-58239, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.2CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.39% · top 67% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.

Affected products

  • Linux · Linux

    • affected 692d7b5d1f9125a1cf0595e979e3b5fb7210547e – < f310143961e2d9a0479fca117ce869f8aaecc140
    • affected 692d7b5d1f9125a1cf0595e979e3b5fb7210547e – < 31e10d6cb0c9532ff070cf50da1657c3acee9276
    • affected 692d7b5d1f9125a1cf0595e979e3b5fb7210547e – < 4338032aa90bd1d5b33a4274e8fa8347cda5ee09
    • affected 692d7b5d1f9125a1cf0595e979e3b5fb7210547e – < 6756168add1c6c3ef1c32c335bb843a5d1f99a75
    • affected 692d7b5d1f9125a1cf0595e979e3b5fb7210547e – < 3b952d8fdfcf6fd8ea0b8954bc9277642cf0977f
    • affected 692d7b5d1f9125a1cf0595e979e3b5fb7210547e – < a4ed943882a8fc057ea5a67643314245e048bbdd
    • affected 692d7b5d1f9125a1cf0595e979e3b5fb7210547e – < fdfbaec5923d9359698cbb286bc0deadbb717504
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 5.4.270 – ≤ 5.4.*
    • unaffected 5.10.211 – ≤ 5.10.*
    • unaffected 5.15.150 – ≤ 5.15.*
    • unaffected 6.1.80 – ≤ 6.1.*
    • unaffected 6.6.19 – ≤ 6.6.*
    • unaffected 6.7.7 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-58239 badge
[![CVE-2024-58239](https://cveledger.app/badge/CVE-2024-58239.svg)](https://cveledger.app/cve/CVE-2024-58239)

Record last updated .