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-93824tls: reject the combination of TLS and sockmap

Description

In the Linux kernel, the following vulnerability has been resolved: tls: reject the combination of TLS and sockmap TLS and sockmap (BPF psock) integration hides a lot of latent bugs. Bugs which may be more or less relevant for real users but they are definitely exploitable. We could not find anyone actively using this integration so let's reject this config. Adding a TLS socket to a sockmap was already rejected by sk_psock_init() through the inet_csk_has_ulp() check. We need to reject the attempts to configure the TLS keys (rather than adding the ULP itself) because checking prior to the ULP installation is tricky without risking a race with sockmap getting added in parallel (sockmap does not hold the socket lock). This patch is a minimal rejection of the feature. Subsequent patch in the series will do a light dead code removal. Full cleanup would require a major rewrite of the Tx path, we don't need skmsg any more.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 9 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected d3b18ad31f93d0b6bae105c679018a1ba7daa9ca – < c4896592744f30ff026f799947c5978bcfd7c8c7
    • affected d3b18ad31f93d0b6bae105c679018a1ba7daa9ca – < e26aa709454d48c3b3ef8d3100c8a04e7d9fd94e
    • affected d3b18ad31f93d0b6bae105c679018a1ba7daa9ca – < c3d4d537337f69e405a36fa561e7292ee4148bf7
    • affected d3b18ad31f93d0b6bae105c679018a1ba7daa9ca – < a08e780b6cc1153cbff8be55de9ec9da809e344f
    • affected d3b18ad31f93d0b6bae105c679018a1ba7daa9ca – < 460e6486617c17dd19abe8f3fc67d9a6fa25f8ca
  • Linux · Linux

    • affected 4.20
    • unaffected < 4.20
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .