What is CVE-2026-46060?

CVE-2026-46060 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, affecting Linux kernel versions from 6.16 onward and patched in 6.18.27, 7.0.4 and 7.1. CVE-2026-46060 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-46060?

CVE-2026-46060 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2026-46060?

Yes, CVE-2026-46060 has been patched. Fixed versions include 6.18.27, 7.0.4 and 7.1. If you are running Linux kernel 6.16 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-46060 actively exploited?

CVE-2026-46060 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-46060

Medium

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.

Package Linux Kernel

Published 2026-05-27

Last modified 2026-06-16

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected versions

Linux kernel versions 6.16 and later are affected. Fixed in 6.18.27, 7.0.4, 7.1 and their respective stable series.

Affected from

≥ 6.16

Fixed in

✓ 6.18.27 6.18.x ✓ 7.0.4 7.0.x ✓ 7.1

References

3 total

Kernel Git
https://git.kernel.org/stable/c/27f561bf894e46bdc2d6209c50884adad79d8277

Patch
Kernel Git
https://git.kernel.org/stable/c/7cd651f1357dcc477e6483c3a4706836b46bdc92

Patch
Kernel Git
https://git.kernel.org/stable/c/95aed2af87ec43fa7624cc81dd13d37824ad4972

Patch

Details

CVE ID CVE-2026-46060

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2026-05-27

Modified 2026-06-16

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-46060?

CVE-2026-46060 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 6.16 onward and has been patched in 6.18.27, 7.0.4 and 7.1. CVE-2026-46060 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-46060?

CVE-2026-46060 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2026-46060?

Yes. CVE-2026-46060 has been patched. Fixed versions include 6.18.27, 7.0.4 and 7.1. If you are running Linux kernel 6.16 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-46060 actively exploited?

No. CVE-2026-46060 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.