CVE-2026-46060 (GCVE-0-2026-46060)

Vulnerability from cvelistv5 – Published: 2026-05-27 12:57 – Updated: 2026-05-27 12:57
VLAI
Title
crypto: qat - fix IRQ cleanup on 6xxx probe failure
Summary
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - fix IRQ cleanup on 6xxx probe failure When adf_dev_up() partially completes and then fails, the IRQ handlers registered during adf_isr_resource_alloc() are not detached before the MSI-X vectors are released. Since the device is enabled with pcim_enable_device(), calling pci_alloc_irq_vectors() internally registers pcim_msi_release() as a devres action. On probe failure, devres runs pcim_msi_release() which calls pci_free_irq_vectors(), tearing down the MSI-X vectors while IRQ handlers (for example 'qat0-bundle0') are still attached. This causes remove_proc_entry() warnings: [ 22.163964] remove_proc_entry: removing non-empty directory 'irq/143', leaking at least 'qat0-bundle0' Moving the devm_add_action_or_reset() before adf_dev_up() does not solve the problem since devres runs in LIFO order and pcim_msi_release(), registered later inside adf_dev_up(), would still fire before adf_device_down(). Fix by calling adf_dev_down() explicitly when adf_dev_up() fails, to properly free IRQ handlers before devres releases the MSI-X vectors.
Severity
No CVSS data available.
Assigner
Impacted products
Vendor Product Version
Linux Linux Affected: 17fd7514ae68c541bf952876ce2005cb4a53f283 , < 27f561bf894e46bdc2d6209c50884adad79d8277 (git)
Affected: 17fd7514ae68c541bf952876ce2005cb4a53f283 , < 7cd651f1357dcc477e6483c3a4706836b46bdc92 (git)
Affected: 17fd7514ae68c541bf952876ce2005cb4a53f283 , < 95aed2af87ec43fa7624cc81dd13d37824ad4972 (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": [
            "drivers/crypto/intel/qat/qat_6xxx/adf_drv.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "27f561bf894e46bdc2d6209c50884adad79d8277",
              "status": "affected",
              "version": "17fd7514ae68c541bf952876ce2005cb4a53f283",
              "versionType": "git"
            },
            {
              "lessThan": "7cd651f1357dcc477e6483c3a4706836b46bdc92",
              "status": "affected",
              "version": "17fd7514ae68c541bf952876ce2005cb4a53f283",
              "versionType": "git"
            },
            {
              "lessThan": "95aed2af87ec43fa7624cc81dd13d37824ad4972",
              "status": "affected",
              "version": "17fd7514ae68c541bf952876ce2005cb4a53f283",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/crypto/intel/qat/qat_6xxx/adf_drv.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: qat - fix IRQ cleanup on 6xxx probe failure\n\nWhen adf_dev_up() partially completes and then fails, the IRQ\nhandlers registered during adf_isr_resource_alloc() are not detached\nbefore the MSI-X vectors are released.\n\nSince the device is enabled with pcim_enable_device(), calling\npci_alloc_irq_vectors() internally registers pcim_msi_release() as a\ndevres action. On probe failure, devres runs pcim_msi_release() which\ncalls pci_free_irq_vectors(), tearing down the MSI-X vectors while IRQ\nhandlers (for example \u0027qat0-bundle0\u0027) are still attached. This causes\nremove_proc_entry() warnings:\n\n    [   22.163964] remove_proc_entry: removing non-empty directory \u0027irq/143\u0027, leaking at least \u0027qat0-bundle0\u0027\n\nMoving the devm_add_action_or_reset() before adf_dev_up() does not solve\nthe problem since devres runs in LIFO order and pcim_msi_release(),\nregistered later inside adf_dev_up(), would still fire before\nadf_device_down().\n\nFix by calling adf_dev_down() explicitly when adf_dev_up() fails, to\nproperly free IRQ handlers before devres releases the MSI-X vectors."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-27T12:57:20.991Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/27f561bf894e46bdc2d6209c50884adad79d8277"
        },
        {
          "url": "https://git.kernel.org/stable/c/7cd651f1357dcc477e6483c3a4706836b46bdc92"
        },
        {
          "url": "https://git.kernel.org/stable/c/95aed2af87ec43fa7624cc81dd13d37824ad4972"
        }
      ],
      "title": "crypto: qat - fix IRQ cleanup on 6xxx probe failure",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-46060",
    "datePublished": "2026-05-27T12:57:20.991Z",
    "dateReserved": "2026-05-13T15:03:33.095Z",
    "dateUpdated": "2026-05-27T12:57:20.991Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-46060",
      "date": "2026-05-29",
      "epss": "0.00017",
      "percentile": "0.04336"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-46060\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-05-27T14:17:25.757\",\"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: qat - fix IRQ cleanup on 6xxx probe failure\\n\\nWhen adf_dev_up() partially completes and then fails, the IRQ\\nhandlers registered during adf_isr_resource_alloc() are not detached\\nbefore the MSI-X vectors are released.\\n\\nSince the device is enabled with pcim_enable_device(), calling\\npci_alloc_irq_vectors() internally registers pcim_msi_release() as a\\ndevres action. On probe failure, devres runs pcim_msi_release() which\\ncalls pci_free_irq_vectors(), tearing down the MSI-X vectors while IRQ\\nhandlers (for example \u0027qat0-bundle0\u0027) are still attached. This causes\\nremove_proc_entry() warnings:\\n\\n    [   22.163964] remove_proc_entry: removing non-empty directory \u0027irq/143\u0027, leaking at least \u0027qat0-bundle0\u0027\\n\\nMoving the devm_add_action_or_reset() before adf_dev_up() does not solve\\nthe problem since devres runs in LIFO order and pcim_msi_release(),\\nregistered later inside adf_dev_up(), would still fire before\\nadf_device_down().\\n\\nFix by calling adf_dev_down() explicitly when adf_dev_up() fails, to\\nproperly free IRQ handlers before devres releases the MSI-X vectors.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/27f561bf894e46bdc2d6209c50884adad79d8277\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/7cd651f1357dcc477e6483c3a4706836b46bdc92\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/95aed2af87ec43fa7624cc81dd13d37824ad4972\",\"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…