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-26800tls: fix use-after-free on failed backlog decryption

Description

In the Linux kernel, the following vulnerability has been resolved: tls: fix use-after-free on failed backlog decryption When the decrypt request goes to the backlog and crypto_aead_decrypt returns -EBUSY, tls_do_decryption will wait until all async decryptions have completed. If one of them fails, tls_do_decryption will return -EBADMSG and tls_decrypt_sg jumps to the error path, releasing all the pages. But the pages have been passed to the async callback, and have already been released by tls_decrypt_done. The only true async case is when crypto_aead_decrypt returns -EINPROGRESS. With -EBUSY, we already waited so we can tell tls_sw_recvmsg that the data is available for immediate copy, but we need to notify tls_decrypt_sg (via the new ->async_done flag) that the memory has already been released.

Timeline

  1. ID reserved

    By Linux

  2. · 45 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-26800, 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.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.74% · top 44% of all CVEs (18 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 cd1bbca03f3c1d845ce274c0d0a66de8e5929f72 – < f2b85a4cc763841843de693bbd7308fe9a2c4c89
    • affected 13eca403876bbea3716e82cdfe6f1e6febb38754 – < 81be85353b0f5a7b660635634b655329b429eefe
    • affected ab6397f072e5097f267abf5cb08a8004e6b17694 – < 1ac9fb84bc7ecd4bc6428118301d9d864d2a58d1
    • affected 8590541473188741055d27b955db0777569438e3 – < 13114dc5543069f7b97991e3b79937b6da05f5b0
    • affected 3ade391adc584f17b5570fd205de3ad029090368
    • affected 5.15.160 – < 5.16
  • Linux · Linux

    • affected 6.6.18 – < 6.6.21
    • affected 6.7.6 – < 6.7.9

References

References4

Sources

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

Badge for a README or a ticket

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

Record last updated .