# CVE-2026-93824: tls: reject the combination of TLS and sockmap

> Local attackers can exploit latent bugs in the Linux kernel TLS and sockmap integration to achieve code execution or privilege escalation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-103568, BELL-CVE-2026-93824, DEBIAN-CVE-2026-93824, GHSA-p3wg-3xj5-pf82, UBUNTU-CVE-2026-93824

## What is CVE-2026-93824?

CVE-2026-93824 is a vulnerability in Linux, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-93824?


## How do I fix CVE-2026-93824?

Apply the vendor's patch.

## Is CVE-2026-93824 being exploited?

There is no known exploitation of CVE-2026-93824 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93824 and fix it if it is affected.

What it is: CVE-2026-93824 is a vulnerability in Linux, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93824 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93824/ (Markdown: https://insights.sbomify.com/CVE-2026-93824/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93824
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93824
- OSV: https://osv.dev/vulnerability/CVE-2026-93824

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93824/
Summaries are generated and may contain mistakes; the official description above is the record.