Vulnerability · Published May 27, 2026 · Assigned by Linux

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

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 2% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.1%top 98.1% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux7.0.4-1DEBIAN-CVE-2026-46060
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-46060
Ubuntu:26.04:LTSlinux7.0.0-27.27UBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-46060
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-46060
Ubuntu:26.04:LTSlinux-aws7.0.0-1008.8UBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-46060
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-46060
Ubuntu:26.04:LTSlinux-azure7.0.0-1010.10UBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-46060
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-46060
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1009.9UBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-46060
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-46060
Ubuntu:26.04:LTSlinux-gcp7.0.0-1007.7UBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-28.28~24.04.1UBUNTU-CVE-2026-46060
Ubuntu:26.04:LTSlinux-ibm7.0.0-1009.9UBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-46060
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1013.13UBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-46060
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1008.8UBUNTU-CVE-2026-46060
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-46060
Ubuntu:26.04:LTSlinux-oracle7.0.0-1007.7UBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-46060
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-46060
Ubuntu:26.04:LTSlinux-raspi7.0.0-1014.14UBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-46060
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-46060
Ubuntu:26.04:LTSlinux-realtime7.0.0-27.27.1UBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-46060
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-46060
Ubuntu:26.04:LTSlinux-riscv7.0.0-27.27.1UBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-46060
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-46060
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-46060

Affected products (as reported)

VendorProductVersions
Linux Linux 17fd7514ae68c541bf952876ce2005cb4a53f283 – before 27f561bf894e46bdc2d6209c50884adad79d827717fd7514ae68c541bf952876ce2005cb4a53f283 – before 7cd651f1357dcc477e6483c3a4706836b46bdc9217fd7514ae68c541bf952876ce2005cb4a53f283 – before 95aed2af87ec43fa7624cc81dd13d37824ad4972
Linux Linux 6.16

References