LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46060: crypto: qat - fix IRQ cleanup on 6xxx probe failure

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2026-46060 is a Linux kernel bug in the Intel QAT crypto driver cleanup path. If a QAT 6xxx device probe partially succeeds and then fails, interrupt handlers may remain attached while MSI-X vectors are released, causing kernel warnings and leaked IRQ proc entries. No public source here indicates active exploitation.

Executive priority

Treat as routine maintenance unless your environment depends on QAT acceleration at scale. Prioritize normal kernel patch cycles for affected systems, especially servers with QAT 6xxx hardware. There is no source-backed evidence of exploitation or broad remote exposure.

Technical view

The flaw is in Linux crypto/qat. During 6xxx probe failure, adf_dev_up() can fail after adf_isr_resource_alloc() registers IRQ handlers. Devres later runs pcim_msi_release(), freeing MSI-X vectors before adf_device_down() detaches handlers. The fix explicitly calls adf_dev_down() when adf_dev_up() fails.

Likely exposure

Exposure appears limited to Linux systems using the QAT driver with affected kernel revisions and QAT 6xxx hardware or probe paths. Systems without this driver or hardware are less likely exposed. The source bundle lists Linux kernel versions and stable commit references, but no CVSS score or CWE.

Exploitation context

The provided sources describe a probe-failure cleanup bug, not a remote attack path. Impact evidence is kernel warnings and leaked IRQ proc entries such as non-empty /proc/irq directories. KEV is false, and no cited source states active exploitation.

Researcher notes

The key condition is adf_dev_up() partial completion followed by failure on QAT 6xxx probe. Validate whether downstream kernels include the explicit adf_dev_down() failure-path fix. Avoid assuming broader impact beyond the cleanup ordering described in the kernel references.

Mitigation direction

  • Apply a vendor kernel update containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes for CVE-2026-46060.
  • If patch status is unclear, follow vendor guidance for QAT driver risk reduction.

Validation and detection

  • Inventory Linux hosts using Intel QAT 6xxx hardware or the qat driver.
  • Compare running kernel builds against vendor advisories and referenced stable commits.
  • Review kernel logs for QAT probe failures and remove_proc_entry IRQ warnings.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-46060 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux17fd7514ae68c541bf952876ce2005cb4a53f283, 17fd7514ae68c541bf952876ce2005cb4a53f283, 17fd7514ae68c541bf952876ce2005cb4a53f283unaffected
LinuxLinux6.16, 0, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.