CVE-2026-93824

tls: reject the combination of TLS and sockmap

State
Published
Severity
Not scored
Published
Sep 24, 2026
Updated
Oct 3, 2026
Reserved
Sep 18, 2026

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • d3b18ad31f93d0b6bae105c679018a1ba7daa9ca to before c4896592744f30ff026f799947c5978bcfd7c8c7Affected
  • d3b18ad31f93d0b6bae105c679018a1ba7daa9ca to before e26aa709454d48c3b3ef8d3100c8a04e7d9fd94eAffected
  • d3b18ad31f93d0b6bae105c679018a1ba7daa9ca to before c3d4d537337f69e405a36fa561e7292ee4148bf7Affected
  • d3b18ad31f93d0b6bae105c679018a1ba7daa9ca to before a08e780b6cc1153cbff8be55de9ec9da809e344fAffected
  • d3b18ad31f93d0b6bae105c679018a1ba7daa9ca to before 460e6486617c17dd19abe8f3fc67d9a6fa25f8caAffected
LinuxLinux
  • 4.20Affected
  • before 4.20Not affected
  • 6.1.189 through 6.1.*Not affected
  • 6.6.158 through 6.6.*Not affected
  • 6.12.111 through 6.12.*Not affected
  • 6.18.53 through 6.18.*Not affected
  • 7.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.