CVE-2026-93824
Received Received - Intake

BaseFortify

Publication date: 2026-09-24

Last updated on: 2026-09-24

Assigner: kernel.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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-24
Last Modified
2026-09-24
Generated
2026-09-24
AI Q&A
2026-09-24
EPSS Evaluated
N/A
NVD
CVE-2026-93824
EUVD
EUVD-2026-86213

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves the rejection of the combination of TLS (Transport Layer Security) and sockmap (BPF psock). The integration of these two features can hide latent bugs that may be exploitable. The patch rejects this configuration to prevent potential issues, as adding a TLS socket to a sockmap was already partially restricted by existing checks.

Detection Guidance

This vulnerability is related to the Linux kernel's TLS and sockmap integration. Detection involves checking kernel configurations and running commands to verify if TLS sockets are being added to sockmaps. Use commands like 'grep CONFIG_TLS /boot/config-$(uname -r)' to check if TLS is enabled and 'ss -tulnp | grep tls' to inspect active TLS sockets. If sockmap is enabled, check 'grep BPF /proc/kallsyms' for BPF-related modules.

Impact Analysis

If exploited, this vulnerability could lead to security issues due to hidden bugs in the TLS and sockmap integration. However, the impact is likely limited since no active use of this integration was found. The main risk is potential instability or unexpected behavior in systems using both TLS and sockmap.

Mitigation Strategies

Immediately update your Linux kernel to the latest stable version that includes the patch for this vulnerability. Disable sockmap if it is enabled by removing related BPF modules or configurations. Review and remove any custom kernel configurations that enable TLS and sockmap integration. Monitor system logs for suspicious activity related to socket operations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-93824. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart