# CVE-2026-93161: crypto: qat - clear AES key schedule from stack

> An attacker with local access could potentially read sensitive AES key material from the kernel stack due to insufficient memory clearing.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102084, BELL-CVE-2026-93161, DEBIAN-CVE-2026-93161, GHSA-jc96-xj7h-vxxp, UBUNTU-CVE-2026-93161

## What is CVE-2026-93161?

CVE-2026-93161 is a vulnerability in Linux, published on 17 Sep 2026. 

### Official description

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

crypto: qat - clear AES key schedule from stack

qat_alg_xts_reverse_key() expands the forward XTS AES key on the stack.
That schedule contains key material and can remain in the stack frame.

Clear the temporary crypto_aes_ctx with memzero_explicit() after the copy.

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


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

Apply the vendor's patch.

## Is CVE-2026-93161 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93161 is a vulnerability in Linux, published on 17 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-93161 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-93161/ (Markdown: https://insights.sbomify.com/CVE-2026-93161/index.md)
```

## Sources

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

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