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.
- 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
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.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-90069 being exploited?
There is no known exploitation of CVE-2026-90069 in the wild and no public exploit code.
Sources
Also known as BELL-CVE-2026-90069, DEBIAN-CVE-2026-90069, GHSA-83j8-g3f3-xgrf, UBUNTU-CVE-2026-90069.