# CVE-2026-90069: crypto: acomp - allocate async request context when cloning

> A memory corruption vulnerability in the Linux kernel crypto subsystem allows out-of-bounds writes, potentially leading to code execution or system crashes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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:** BELL-CVE-2026-90069, DEBIAN-CVE-2026-90069, GHSA-83j8-g3f3-xgrf, UBUNTU-CVE-2026-90069

## What is CVE-2026-90069?

CVE-2026-90069 is a high-severity memory corruption 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: acomp - allocate async request context when cloning

ACOMP_REQUEST_ON_STACK() reserves only enough storage for the
synchronous fallback. When an async implementation is selected, callers
clone that stack request before retrying, but acomp_request_clone()
currently copies only the stack-sized object. The clone therefore has no
storage for the async provider request context, and providers such as QAT
write past the allocation through acomp_request_ctx(). KASAN does report
a slab OOB write.

Allocate a zeroed clone large enough for the runtime acomp request size,
copy only the bytes present in the source object, and preserve the
existing fallback-on-allocation-failure behavior. Use the runtime reqsize
because an implementation may adjust it during tfm initialization.

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


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

Apply the vendor's patch.

## Is CVE-2026-90069 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90069 is a high-severity memory corruption 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-90069 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-90069/ (Markdown: https://insights.sbomify.com/CVE-2026-90069/index.md)
```

## Sources

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

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