CVE-2026-46081 (GCVE-0-2026-46081)

Vulnerability from cvelistv5 – Published: 2026-05-27 12:58 – Updated: 2026-05-27 12:58
VLAI
Title
crypto: acomp - fix wrong pointer stored by acomp_save_req()
Summary
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.
Severity
No CVSS data available.
Assigner
Impacted products
Vendor Product Version
Linux Linux Affected: 64929fe8c0a43508eee952cf57903a61c52601e7 , < 343a5bf68a8ff9affcf2b70677ea4cf40c195ee4 (git)
Affected: 64929fe8c0a43508eee952cf57903a61c52601e7 , < 1a2785e5985627f2265ba7775949601a29ba0d1e (git)
Affected: 64929fe8c0a43508eee952cf57903a61c52601e7 , < d7e20b9bd6c990773cf0c09e2642250b8a70263d (git)
Create a notification for this product.
Linux Linux Affected: 6.16
Unaffected: 0 , < 6.16 (semver)
Unaffected: 6.18.27 , ≤ 6.18.* (semver)
Unaffected: 7.0.4 , ≤ 7.0.* (semver)
Unaffected: 7.1-rc1 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "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 \u0026req-\u003echain in req-\u003ebase.data. When\nacomp_reqchain_done() is invoked on asynchronous completion, it receives\n\u0026req-\u003echain 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   \u003cIRQ\u003e\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   \u003c/IRQ\u003e\n\nFix this by storing the request itself in req-\u003ebase.data instead of\n\u0026req-\u003echain, so that acomp_reqchain_done() receives the correct pointer.\nSimplify acomp_restore_req() accordingly to access req-\u003echain 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",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-46081",
      "date": "2026-05-29",
      "epss": "0.00017",
      "percentile": "0.04336"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-46081\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-05-27T14:17:29.510\",\"lastModified\":\"2026-05-27T14:48:03.013\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"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 \u0026req-\u003echain in req-\u003ebase.data. When\\nacomp_reqchain_done() is invoked on asynchronous completion, it receives\\n\u0026req-\u003echain 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   \u003cIRQ\u003e\\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   \u003c/IRQ\u003e\\n\\nFix this by storing the request itself in req-\u003ebase.data instead of\\n\u0026req-\u003echain, so that acomp_reqchain_done() receives the correct pointer.\\nSimplify acomp_restore_req() accordingly to access req-\u003echain directly.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/1a2785e5985627f2265ba7775949601a29ba0d1e\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/343a5bf68a8ff9affcf2b70677ea4cf40c195ee4\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/d7e20b9bd6c990773cf0c09e2642250b8a70263d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…