CVE-2026-93824

tls: reject the combination of TLS and sockmap

N/A
Published: September 24, 2026 at 04:03 PM UTC
Updated: October 3, 2026 at 11:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.20 ≤ v < 6.1.1894.20 ≤ v < 6.12.1114.20 ≤ v < 6.18.534.20 ≤ v < 6.6.1584.20 ≤ v < 7.24.20d3b18ad31f93d0b6bae105c679018a1ba7daa9ca
Vendor states this is fixed in 460e6486617c17dd19abe8f3fc67d9a6fa25f8ca (fixed)
Vendor states this is fixed in a08e780b6cc1153cbff8be55de9ec9da809e344f (fixed)
Vendor states this is fixed in c3d4d537337f69e405a36fa561e7292ee4148bf7 (fixed)
Vendor states this is fixed in c4896592744f30ff026f799947c5978bcfd7c8c7 (fixed)
Vendor states this is fixed in e26aa709454d48c3b3ef8d3100c8a04e7d9fd94e (fixed)
Vendor states this is fixed in 4.20 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card