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

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.

Affected packages & fixed versions

Affected products (as reported)

References

• https://git.kernel.org/stable/c/d48197cbd5d3476c7deea644972e9ec510865ec2
• https://git.kernel.org/stable/c/889fa17a0af09ff93a9166abc82ee7a654faa49b
• https://git.kernel.org/stable/c/ee440d4fc0d2f15894ab1f64c474a3adbc858880