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-26583tls: fix race between async notify and socket close

Description

In the Linux kernel, the following vulnerability has been resolved: tls: fix race between async notify and socket close The submitting thread (one which called recvmsg/sendmsg) may exit as soon as the async crypto handler calls complete() so any code past that point risks touching already freed data. Try to avoid the locking and extra flags altogether. Have the main thread hold an extra reference, this way we can depend solely on the atomic ref counter for synchronization. Don't futz with reiniting the completion, either, we are now tightly controlling when completion fires.

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

  3. · 2 years 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-26583, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.55% · top 53% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 0cada33241d9de205522e3858b18e506ca5cce2c – < f17d21ea73918ace8afb9c2d8e734dbf71c2c9d7
    • affected 0cada33241d9de205522e3858b18e506ca5cce2c – < 7a3ca06d04d589deec81f56229a9a9d62352ce01
    • affected 0cada33241d9de205522e3858b18e506ca5cce2c – < 86dc27ee36f558fe223dbdfbfcb6856247356f4a
    • affected 0cada33241d9de205522e3858b18e506ca5cce2c – < 6209319b2efdd8524691187ee99c40637558fa33
    • affected 0cada33241d9de205522e3858b18e506ca5cce2c – < aec7961916f3f9e88766e2688992da6980f11b8d
    • affected cf4cc95a15f599560c7abd89095a7973a4b9cec3
    • affected 9b81d43da15e56ed89f083f326561acdcaf549ce
    • affected 5.4.44 – < 5.5
    • affected 5.6.16 – < 5.7
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.15.160 – ≤ 5.15.*
    • unaffected 6.1.79 – ≤ 6.1.*
    • unaffected 6.6.18 – ≤ 6.6.*
    • unaffected 6.7.6 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .