# CVE-2026-46081: linux: In the Linux kernel, the following vulnerability has been resolved: crypto: acomp - fix wrong pointer stored by acom... CVE-2026-46081 is fixed in 19 products on 1 platform, first by ALAS2023-2026-1754, released May 25, 2026. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2026-46081 - Priority: High - CVSS: 7.8 (high) - EPSS: 0.0017 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: May 25, 2026 ## Description 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: 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 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. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool6.18 amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | kernel-livepatch-6.18.30-61.116 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | kernel6.18 amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | kernel6.18-devel amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | kernel6.18-headers amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | kernel6.18-tools amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | linux Debian 14 | 7.0.4-1 | [DEBIAN-CVE-2026-46081](https://patchblox.com/security/data/fix/linux/debian-cve-2026-46081.md) | May 27, 2026 | | Linux | perf6.18 amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | python3-perf6.18 amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | | Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.30-61.116.amzn2023 | [ALAS2023-2026-1754](https://patchblox.com/security/data/fix/linux/alas2023-2026-1754.md) | May 25, 2026 | --- Data as of 2026-11-08T19:12:23Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.