Answer in brief
CVE-2026-90069 records a High severity (CVSS 7.8) vulnerability in crypto: acomp - allocate async request context when cloning. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=097c432caaa6d91f87732fe991cb08139e31101a <d48197cbd5d3476c7deea644972e9ec510865ec2 || >=097c432caaa6d91f87732fe991cb08139e31101a <889fa17a0af09ff93a9166abc82ee7a654faa49b || >=097c432caaa6d91f87732fe991cb08139e31101a <ee440d4fc0d2f15894ab1f64c474a3adbc858880 | d48197cbd5d3476c7deea644972e9ec510865ec2, 889fa17a0af09ff93a9166abc82ee7a654faa49b, ee440d4fc0d2f15894ab1f64c474a3adbc858880 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.