Skip to main content
VulnerabilityPublished Updated

CVE-2026-46060: Linux kernel · crypto: qat – fix IRQ cleanup on 6xxx probe failure

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in 95aed2af87ec43fa7624cc81dd13d37824ad4972 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in 95aed2af87ec43fa7624cc81dd13d37824ad4972, 27f561bf894e46bdc2d6209c50884adad79d8277, 7cd651f1357dcc477e6483c3a4706836b46bdc92

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade Linux kernel to 95aed2af87ec43fa7624cc81dd13d37824ad4972, 27f561bf894e46bdc2d6209c50884adad79d8277 or 7cd651f1357dcc477e6483c3a4706836b46bdc92.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 17fd7514ae68c541bf952876ce2005cb4a53f283, < 95aed2af87ec43fa7624cc81dd13d37824ad4972
Fixed in
  • 95aed2af87ec43fa7624cc81dd13d37824ad4972
LinuxLinuxAffected
  • ≥ 17fd7514ae68c541bf952876ce2005cb4a53f283, < 27f561bf894e46bdc2d6209c50884adad79d8277
Fixed in
  • 27f561bf894e46bdc2d6209c50884adad79d8277
LinuxLinuxAffected
  • ≥ 17fd7514ae68c541bf952876ce2005cb4a53f283, < 7cd651f1357dcc477e6483c3a4706836b46bdc92
Fixed in
  • 7cd651f1357dcc477e6483c3a4706836b46bdc92
LinuxLinuxAffected
  • =6.16
Fixed in–

Description

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.

References

Community reviews

Loading reviews…