CVE-2026-46081

published 27 May 2026 · updated 5 Aug 2026

crypto: acomp - fix wrong pointer stored by acomp_save_req()

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1a2785e5985627f2265ba7775949601a29ba0d1e, Kernel 343a5bf68a8ff9affcf2b70677ea4cf40c195ee4 and Kernel d7e20b9bd6c990773cf0c09e2642250b8a70263d.

In the Linux kernel, the following vulnerability has been resolved: crypto: acomp - fix wrong pointer stored by acomp_save_req() acomp_save_req() stores &req->chain in req->base.data. When acomp_reqchain_done() is invoked on asynchronous completion, it receives &req->chain as the data argument but casts it directly to struct acomp_req. Since data points to the chain member, all subsequent field accesses are at a wrong offset, resulting in memory corruption. The issue occurs when an asynchronous hardware implementation, such as the QAT driver, completes a request that uses the DMA virtual address interface (e.g. acomp_request_set_src_dma()). This combination causes crypto_acomp_compress() to enter the acomp_do_req_chain() path, which sets acomp_reqchain_done() as the completion callback via acomp_save_req(). With KASAN enabled, this manifests as a general protection fault in acomp_reqchain_done(): general protection fault, probably for non-canonical address 0xe000040000000000 KASAN: probably user-memory-access in range [0x0000400000000000-0x0000400000000007] RIP: 0010:acomp_reqchain_done+0x15b/0x4e0 Call Trace: <IRQ> qat_comp_alg_callback+0x5d/0xa0 [intel_qat] adf_ring_response_handler+0x376/0x8b0 [intel_qat] adf_response_handler+0x60/0x170 [intel_qat] tasklet_action_common+0x223/0x820 handle_softirqs+0x1ab/0x640 </IRQ> Fix this by storing the request itself in req->base.data instead of &req->chain, so that acomp_reqchain_done() receives the correct pointer. Simplify acomp_restore_req() accordingly to access req->chain directly.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.16, >=64929fe8c0a43508eee952cf57903a61c52601e7 <1a2785e5985627f2265ba7775949601a29ba0d1e, >=64929fe8c0a43508eee952cf57903a61c52601e7 <343a5bf68a8ff9affcf2b70677ea4cf40c195ee4, >=64929fe8c0a43508eee952cf57903a61c52601e7 <d7e20b9bd6c990773cf0c09e2642250b8a70263d1a2785e5985627f2265ba7775949601a29ba0d1e, 343a5bf68a8ff9affcf2b70677ea4cf40c195ee4, d7e20b9bd6c990773cf0c09e2642250b8a70263d

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-46081 severity on Zeptric[![CVE-2026-46081](https://zeptric.io/badge/cve/CVE-2026-46081.svg)](https://zeptric.io/cve/CVE-2026-46081)