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-2026-31533net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption

Description

In the Linux kernel, the following vulnerability has been resolved: net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption The -EBUSY handling in tls_do_encryption(), introduced by commit 859054147318 ("net: tls: handle backlogging of crypto requests"), has a use-after-free due to double cleanup of encrypt_pending and the scatterlist entry. When crypto_aead_encrypt() returns -EBUSY, the request is enqueued to the cryptd backlog and the async callback tls_encrypt_done() will be invoked upon completion. That callback unconditionally restores the scatterlist entry (sge->offset, sge->length) and decrements ctx->encrypt_pending. However, if tls_encrypt_async_wait() returns an error, the synchronous error path in tls_do_encryption() performs the same cleanup again, double-decrementing encrypt_pending and double-restoring the scatterlist. The double-decrement corrupts the encrypt_pending sentinel (initialized to 1), making tls_encrypt_async_wait() permanently skip the wait for pending async callbacks. A subsequent sendmsg can then free the tls_rec via bpf_exec_tx_verdict() while a cryptd callback is still pending, resulting in a use-after-free when the callback fires on the freed record. Fix this by skipping the synchronous cleanup when the -EBUSY async wait returns an error, since the callback has already handled encrypt_pending and sge restoration.

Timeline

  1. ID reserved

    By Linux

  2. · 45 days later

    Published

  3. · 7 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-2026-31533, 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.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.40% · top 65% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
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 3ade391adc584f17b5570fd205de3ad029090368 – < 414fc5e5a5aff776c150f1b86770e0a25a35df3a
    • affected cd1bbca03f3c1d845ce274c0d0a66de8e5929f72 – < 02f3ecadb23558bbe068e6504118f1b712d4ece0
    • affected 13eca403876bbea3716e82cdfe6f1e6febb38754 – < 0e43e0a3c94044acc74b8e0927c27972eb5a59e8
    • affected 8590541473188741055d27b955db0777569438e3 – < aa9facde6c5005205874c37db3fd25799d741baf
    • affected 8590541473188741055d27b955db0777569438e3 – < 5d70eb25b41e9b010828cd12818b06a0c3b04412
    • affected 8590541473188741055d27b955db0777569438e3 – < 2694d408b0e595024e0fc1d64ff9db0358580f74
    • affected 8590541473188741055d27b955db0777569438e3 – < a9b8b18364fffce4c451e6f6fd218fa4ab646705
    • affected ab6397f072e5097f267abf5cb08a8004e6b17694
    • affected 5.15.160 – < 5.15.203
    • affected 6.1.84 – < 6.1.169
    • affected 6.6.18 – < 6.6.135
    • affected 6.7.6 – < 6.8
  • Linux · Linux

    • affected 6.8
    • unaffected < 6.8
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.169 – ≤ 6.1.*
    • unaffected 6.6.135 – ≤ 6.6.*
    • unaffected 6.12.82 – ≤ 6.12.*
    • unaffected 6.18.23 – ≤ 6.18.*
    • unaffected 6.19.13 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .