Linux
crypto: acomp - allocate async request context when cloning
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 097c432caaa6d91f87732fe991cb08139e31101a, < d48197cbd5d3476c7deea644972e9ec510865ec2
- >= 097c432caaa6d91f87732fe991cb08139e31101a, < 889fa17a0af09ff93a9166abc82ee7a654faa49b
- >= 097c432caaa6d91f87732fe991cb08139e31101a, < ee440d4fc0d2f15894ab1f64c474a3adbc858880
Fixed in d48197cbd5d3476c7deea644972e9ec510865ec2, 889fa17a0af09ff93a9166abc82ee7a654faa49b, ee440d4fc0d2f15894ab1f64c474a3adbc858880
- 6.16
Fixed in 0, 6.18.52, 7.2.6, 7.3
Mitigation
Upgrade Linux to d48197cbd5d3476c7deea644972e9ec510865ec2 or 889fa17a0af09ff93a9166abc82ee7a654faa49b or ee440d4fc0d2f15894ab1f64c474a3adbc858880 or later.
Upgrade Linux to 0 or 6.18.52 or 7.2.6 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.