# CVE-2026-93158: crypto: sa2ul - stop probe if context pool creation fails

> A flaw in the Linux kernel's sa2ul crypto driver allows denial of service if DMA pool creation fails during probe, requiring a kernel patch.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102162, BELL-CVE-2026-93158, DEBIAN-CVE-2026-93158, GHSA-x4wf-3pq8-hcp4, UBUNTU-CVE-2026-93158

## What is CVE-2026-93158?

CVE-2026-93158 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

crypto: sa2ul - stop probe if context pool creation fails

sa_ul_probe() calls sa_init_mem() to create the DMA pool used for
security context buffers, but ignores its return value. If pool creation
fails, probe still continues with DMA setup, algorithm registration and
child population even though later request setup depends on that pool.

Stop probing when sa_init_mem() fails, and route that failure to the PM
cleanup path without attempting to destroy an uncreated DMA pool.

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


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

Apply the vendor's patch.

## Is CVE-2026-93158 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93158 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93158 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-93158/ (Markdown: https://insights.sbomify.com/CVE-2026-93158/index.md)
```

## Sources

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

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