CVE-2026-46060

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (3)

Auto-updated Jun 16, 2026
No patch confirmed yet.
generic

crypto: qat - fix IRQ cleanup on 6xxx probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95aed2af87ec43fa7624cc81dd13d37824ad4972
generic

crypto: qat - fix IRQ cleanup on 6xxx probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7cd651f1357dcc477e6483c3a4706836b46bdc92
generic

crypto: qat - fix IRQ cleanup on 6xxx probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-46060(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (134 versions)7.0.4-1

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 8× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 207 total refreshes for this CVE.

  1. 2026-09-14 07:59 UTCEG score recompute
  2. 2026-09-14 07:59 UTCVendor advisory
  3. 2026-09-14 07:59 UTCGHSA enrichment
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-13 03:39 UTCOSV refresh
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 09:37 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 05:23 UTCEG score recompute
  22. 2026-08-25 05:23 UTCVendor advisory
  23. 2026-08-25 05:23 UTCGHSA enrichment
  24. 2026-08-23 15:09 UTCEG score recompute
  25. 2026-08-23 15:09 UTCVendor advisory
Show 75 more
  1. 2026-08-23 15:08 UTCGHSA enrichment
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-21 20:39 UTCEG score recompute
  5. 2026-08-21 20:39 UTCVendor advisory
  6. 2026-08-21 20:39 UTCGHSA enrichment
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 11:24 UTCEG score recompute
  9. 2026-08-20 11:24 UTCVendor advisory
  10. 2026-08-20 11:24 UTCGHSA enrichment
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 09:18 UTCEG score recompute
  15. 2026-08-17 09:18 UTCVendor advisory
  16. 2026-08-17 09:18 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:50 UTCEG score recompute
  19. 2026-08-16 02:50 UTCVendor advisory
  20. 2026-08-16 02:50 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-15 00:01 UTCVendor advisory
  24. 2026-08-15 00:01 UTCGHSA enrichment
  25. 2026-08-14 01:28 UTCEG score recompute
  26. 2026-08-14 01:28 UTCVendor advisory
  27. 2026-08-14 01:28 UTCGHSA enrichment
  28. 2026-08-13 22:00 UTCEPSS rescore
  29. 2026-08-12 21:26 UTCEG score recompute
  30. 2026-08-12 21:26 UTCVendor advisory
  31. 2026-08-12 21:26 UTCGHSA enrichment
  32. 2026-08-12 13:51 UTCEPSS rescore
  33. 2026-08-11 22:52 UTCEG score recompute
  34. 2026-08-11 22:52 UTCVendor advisory
  35. 2026-08-11 22:52 UTCGHSA enrichment
  36. 2026-08-11 00:13 UTCEG score recompute
  37. 2026-08-11 00:13 UTCVendor advisory
  38. 2026-08-11 00:13 UTCGHSA enrichment
  39. 2026-08-11 00:00 UTCEPSS rescore
  40. 2026-08-09 19:59 UTCEG score recompute
  41. 2026-08-09 19:59 UTCVendor advisory
  42. 2026-08-09 19:59 UTCGHSA enrichment
  43. 2026-08-09 13:46 UTCEPSS rescore
  44. 2026-08-08 21:26 UTCEG score recompute
  45. 2026-08-08 21:26 UTCVendor advisory
  46. 2026-08-08 21:26 UTCGHSA enrichment
  47. 2026-08-08 16:37 UTCEPSS rescore
  48. 2026-08-07 18:01 UTCEG score recompute
  49. 2026-08-07 18:01 UTCVendor advisory
  50. 2026-08-07 18:01 UTCGHSA enrichment
  51. 2026-08-06 19:27 UTCEG score recompute
  52. 2026-08-06 19:27 UTCVendor advisory
  53. 2026-08-06 19:27 UTCGHSA enrichment
  54. 2026-08-06 13:47 UTCEPSS rescore
  55. 2026-08-05 20:53 UTCEG score recompute
  56. 2026-08-05 20:53 UTCVendor advisory
  57. 2026-08-05 20:53 UTCGHSA enrichment
  58. 2026-08-05 19:17 UTCEPSS rescore
  59. 2026-08-04 15:10 UTCEPSS rescore
  60. 2026-08-04 10:39 UTCEPSS rescore
  61. 2026-08-03 16:27 UTCEG score recompute
  62. 2026-08-03 16:27 UTCVendor advisory
  63. 2026-08-03 16:27 UTCGHSA enrichment
  64. 2026-08-03 10:36 UTCEPSS rescore
  65. 2026-08-02 13:55 UTCEG score recompute
  66. 2026-08-02 13:55 UTCVendor advisory
  67. 2026-08-02 13:55 UTCGHSA enrichment
  68. 2026-08-02 02:27 UTCEPSS rescore
  69. 2026-08-01 15:21 UTCEG score recompute
  70. 2026-08-01 15:21 UTCVendor advisory
  71. 2026-08-01 15:21 UTCGHSA enrichment
  72. 2026-08-01 04:16 UTCEPSS rescore
  73. 2026-07-31 07:30 UTCEG score recompute
  74. 2026-07-31 07:30 UTCVendor advisory
  75. 2026-07-31 07:30 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-46060?
CVE-2026-46060 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: qat - fix IRQ cleanup on 6xxx probe failure When adfdevup() partially completes and then fails, the IRQ handlers registered during adfisrresource_alloc() are not detached before the MSI-X vectors are released. Since the…
When was CVE-2026-46060 disclosed?
CVE-2026-46060 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46060 actively exploited?
CVE-2026-46060 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-46060?
CVE-2026-46060 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46060?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46060, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46060

Explore →

Is Your Infrastructure Affected by CVE-2026-46060?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.