CVE-2026-64529

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

crypto: qat - remove unused character device and IOCTLs

The QAT driver exposes a character device (qat_adf_ctl) with IOCTLs for device configuration, start, stop, status query and enumeration. These IOCTLs are not part of any public uAPI header and have no known in-tree or out-of-tree users. Device lifecycle is already managed via sysfs.

The ioctl interface also increases the attack surface and is the subject of a number of bug reports.

Remove the character device, the IOCTL definitions, and the related data structures (adf_dev_status_info, adf_user_cfg_key_val, adf_user_cfg_section, adf_user_cfg_ctl_data). Drop the now-unused adf_cfg_user.h header and strip adf_ctl_drv.c down to the minimal module_init/module_exit hooks for workqueue, AER, and crypto/compression algorithm registration.

Clean up leftover dead code that was only reachable from the removed IOCTL paths: adf_cfg_del_all(), adf_devmgr_verify_id(), adf_devmgr_get_num_dev(), adf_devmgr_get_dev_by_id(), adf_get_vf_real_id() and the unused ADF_CFG macros.

Additionally, drop the entry associated to QAT IOCTLs in ioctl-number.rst.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (9)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

crypto: qat - remove unused character device and IOCTLs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/de2cc38489b629927910b1aeff69bba7bd5c6f1b
generic

crypto: qat - remove unused character device and IOCTLs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d237230728c567297f2f98b425d63156ab2ed17f
generic

crypto: qat - remove unused character device and IOCTLs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b8ebf008696de1ec08c90d51f94d7e40bd448be1
generic

crypto: qat - remove unused character device and IOCTLs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b1ea97076bd0a5196290deba172034e480646727
generic

crypto: qat - remove unused character device and IOCTLs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a4999664a5ef77bdb0c6e6b935f581ac8ce6b63a
generic

crypto: qat - remove unused character device and IOCTLs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6848a6e39cac44fdb7cb88f0f777df62172d1551
generic

crypto: qat - remove unused character device and IOCTLs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3ae49dd04dbb11fb73f17f58a982dba128abe83a
generic

crypto: qat - remove unused character device and IOCTLs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1de076f43e64bf65fbe7280a269c70e0e60518df
generic

crypto: qat - remove unused character device and IOCTLs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/071590a44cbc38483fceb1ab943363ec26868e1b

Vendor Advisories for CVE-2026-64529(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-15ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-15ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-15ubuntu

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1
linux-6.16.1.106-3~deb11u1 ... 6.1.176-1~deb11u1 (21 versions)6.1.177-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)6.1.177-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (146 versions)7.0.14-1

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 30× in last 7d / 103× 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 202 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64529?
CVE-2026-64529 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: qat - remove unused character device and IOCTLs The QAT driver exposes a character device (qatadfctl) with IOCTLs for device configuration, start, stop, status query and enumeration. These IOCTLs are not part of any public…
When was CVE-2026-64529 disclosed?
CVE-2026-64529 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64529 actively exploited?
CVE-2026-64529 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 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-64529?
CVE-2026-64529 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64529?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64529, 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-64529

Explore →

Is Your Infrastructure Affected by CVE-2026-64529?

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