{"api_version":"1","generated_at":"2026-05-27T22:56:53+00:00","cve":"CVE-2026-46081","urls":{"html":"https://cve.report/CVE-2026-46081","api":"https://cve.report/api/cve/CVE-2026-46081.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-46081","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-46081"},"summary":{"title":"crypto: acomp - fix wrong pointer stored by acomp_save_req()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: acomp - fix wrong pointer stored by acomp_save_req()\n\nacomp_save_req() stores &req->chain in req->base.data. When\nacomp_reqchain_done() is invoked on asynchronous completion, it receives\n&req->chain as the data argument but casts it directly to struct\nacomp_req. Since data points to the chain member, all subsequent field\naccesses are at a wrong offset, resulting in memory corruption.\n\nThe issue occurs when an asynchronous hardware implementation, such as\nthe QAT driver, completes a request that uses the DMA virtual address\ninterface (e.g. acomp_request_set_src_dma()). This combination causes\ncrypto_acomp_compress() to enter the acomp_do_req_chain() path, which\nsets acomp_reqchain_done() as the completion callback via\nacomp_save_req().\n\nWith KASAN enabled, this manifests as a general protection fault in\nacomp_reqchain_done():\n\n  general protection fault, probably for non-canonical address 0xe000040000000000\n  KASAN: probably user-memory-access in range [0x0000400000000000-0x0000400000000007]\n  RIP: 0010:acomp_reqchain_done+0x15b/0x4e0\n  Call Trace:\n   <IRQ>\n   qat_comp_alg_callback+0x5d/0xa0 [intel_qat]\n   adf_ring_response_handler+0x376/0x8b0 [intel_qat]\n   adf_response_handler+0x60/0x170 [intel_qat]\n   tasklet_action_common+0x223/0x820\n   handle_softirqs+0x1ab/0x640\n   </IRQ>\n\nFix this by storing the request itself in req->base.data instead of\n&req->chain, so that acomp_reqchain_done() receives the correct pointer.\nSimplify acomp_restore_req() accordingly to access req->chain directly.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-05-27 14:17:29","updated_at":"2026-05-27 14:48:03"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/343a5bf68a8ff9affcf2b70677ea4cf40c195ee4","name":"https://git.kernel.org/stable/c/343a5bf68a8ff9affcf2b70677ea4cf40c195ee4","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/1a2785e5985627f2265ba7775949601a29ba0d1e","name":"https://git.kernel.org/stable/c/1a2785e5985627f2265ba7775949601a29ba0d1e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/d7e20b9bd6c990773cf0c09e2642250b8a70263d","name":"https://git.kernel.org/stable/c/d7e20b9bd6c990773cf0c09e2642250b8a70263d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-46081","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46081","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 64929fe8c0a43508eee952cf57903a61c52601e7 343a5bf68a8ff9affcf2b70677ea4cf40c195ee4 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 64929fe8c0a43508eee952cf57903a61c52601e7 1a2785e5985627f2265ba7775949601a29ba0d1e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 64929fe8c0a43508eee952cf57903a61c52601e7 d7e20b9bd6c990773cf0c09e2642250b8a70263d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.16","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.16 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.27 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.4 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["crypto/acompress.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"343a5bf68a8ff9affcf2b70677ea4cf40c195ee4","status":"affected","version":"64929fe8c0a43508eee952cf57903a61c52601e7","versionType":"git"},{"lessThan":"1a2785e5985627f2265ba7775949601a29ba0d1e","status":"affected","version":"64929fe8c0a43508eee952cf57903a61c52601e7","versionType":"git"},{"lessThan":"d7e20b9bd6c990773cf0c09e2642250b8a70263d","status":"affected","version":"64929fe8c0a43508eee952cf57903a61c52601e7","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["crypto/acompress.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.16"},{"lessThan":"6.16","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.27","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.27","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.4","versionStartIncluding":"6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1-rc1","versionStartIncluding":"6.16","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: acomp - fix wrong pointer stored by acomp_save_req()\n\nacomp_save_req() stores &req->chain in req->base.data. When\nacomp_reqchain_done() is invoked on asynchronous completion, it receives\n&req->chain as the data argument but casts it directly to struct\nacomp_req. Since data points to the chain member, all subsequent field\naccesses are at a wrong offset, resulting in memory corruption.\n\nThe issue occurs when an asynchronous hardware implementation, such as\nthe QAT driver, completes a request that uses the DMA virtual address\ninterface (e.g. acomp_request_set_src_dma()). This combination causes\ncrypto_acomp_compress() to enter the acomp_do_req_chain() path, which\nsets acomp_reqchain_done() as the completion callback via\nacomp_save_req().\n\nWith KASAN enabled, this manifests as a general protection fault in\nacomp_reqchain_done():\n\n  general protection fault, probably for non-canonical address 0xe000040000000000\n  KASAN: probably user-memory-access in range [0x0000400000000000-0x0000400000000007]\n  RIP: 0010:acomp_reqchain_done+0x15b/0x4e0\n  Call Trace:\n   <IRQ>\n   qat_comp_alg_callback+0x5d/0xa0 [intel_qat]\n   adf_ring_response_handler+0x376/0x8b0 [intel_qat]\n   adf_response_handler+0x60/0x170 [intel_qat]\n   tasklet_action_common+0x223/0x820\n   handle_softirqs+0x1ab/0x640\n   </IRQ>\n\nFix this by storing the request itself in req->base.data instead of\n&req->chain, so that acomp_reqchain_done() receives the correct pointer.\nSimplify acomp_restore_req() accordingly to access req->chain directly."}],"providerMetadata":{"dateUpdated":"2026-05-27T12:58:19.498Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/343a5bf68a8ff9affcf2b70677ea4cf40c195ee4"},{"url":"https://git.kernel.org/stable/c/1a2785e5985627f2265ba7775949601a29ba0d1e"},{"url":"https://git.kernel.org/stable/c/d7e20b9bd6c990773cf0c09e2642250b8a70263d"}],"title":"crypto: acomp - fix wrong pointer stored by acomp_save_req()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-46081","datePublished":"2026-05-27T12:58:19.498Z","dateReserved":"2026-05-13T15:03:33.096Z","dateUpdated":"2026-05-27T12:58:19.498Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-05-27 14:17:29","lastModifiedDate":"2026-05-27 14:48:03","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"46081","Ordinal":"1","Title":"crypto: acomp - fix wrong pointer stored by acomp_save_req()","CVE":"CVE-2026-46081","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"46081","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: acomp - fix wrong pointer stored by acomp_save_req()\n\nacomp_save_req() stores &req->chain in req->base.data. When\nacomp_reqchain_done() is invoked on asynchronous completion, it receives\n&req->chain as the data argument but casts it directly to struct\nacomp_req. Since data points to the chain member, all subsequent field\naccesses are at a wrong offset, resulting in memory corruption.\n\nThe issue occurs when an asynchronous hardware implementation, such as\nthe QAT driver, completes a request that uses the DMA virtual address\ninterface (e.g. acomp_request_set_src_dma()). This combination causes\ncrypto_acomp_compress() to enter the acomp_do_req_chain() path, which\nsets acomp_reqchain_done() as the completion callback via\nacomp_save_req().\n\nWith KASAN enabled, this manifests as a general protection fault in\nacomp_reqchain_done():\n\n  general protection fault, probably for non-canonical address 0xe000040000000000\n  KASAN: probably user-memory-access in range [0x0000400000000000-0x0000400000000007]\n  RIP: 0010:acomp_reqchain_done+0x15b/0x4e0\n  Call Trace:\n   <IRQ>\n   qat_comp_alg_callback+0x5d/0xa0 [intel_qat]\n   adf_ring_response_handler+0x376/0x8b0 [intel_qat]\n   adf_response_handler+0x60/0x170 [intel_qat]\n   tasklet_action_common+0x223/0x820\n   handle_softirqs+0x1ab/0x640\n   </IRQ>\n\nFix this by storing the request itself in req->base.data instead of\n&req->chain, so that acomp_reqchain_done() receives the correct pointer.\nSimplify acomp_restore_req() accordingly to access req->chain directly.","Type":"Description","Title":"crypto: acomp - fix wrong pointer stored by acomp_save_req()"}]}}}