Vulnerability · CVE-2026-64305
crypto: qat - protect service table iterations with service_lock
Published Jul 25, 2026 · catalog updated Oct 26, 2026 · crypto: qat - protect
Last checked Oct 31, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-64305. EPSS is 0.13%. Act only if a listed version of crypto: qat - protect is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (crypto: qat - protect).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.13%
- Remediation
- Advisory link
- Affected products
- Linux Kernel
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - protect service table iterations with service_lock The service_table list is protected by service_lock when entries are added or removed (in adf_service_add() and adf_service_remove()), but several functions iterate over the list without holding this lock. A concurrent adf_service_register() or adf_service_unregister() call could modify the list during traversal, leading to list corruption or a use-after-free. Fix this by holding service_lock across all list_for_each_entry() iterations of service_table in adf_dev_init(), adf_dev_start(), adf_dev_stop(), adf_dev_shutdown(), adf_dev_restarting_notify(), adf_dev_restarted_notify(), and adf_error_notifier(). The lock ordering is safe: callers of the static helpers (adf_dev_up() and adf_dev_down()) acquire state_lock before service_lock, and no event_hld callback or service_lock holder ever acquires state_lock in the reverse order.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Linux Kernel3.17.0 → 6.6.160; 6.7.0 → 6.12.96; 6.13.0 → 6.18.39
How to fix CVE-2026-64305
Upgrade
CVE-2026-64305 lists a fix boundary at 6.6.160. Compare the installed build with that boundary before you change production.
Version check
Seen in 3.17.0 → 6.6.160; 6.7.0 → 6.12.96; 6.13.0 → 6.18.39
Advisory
Open the bsi record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-64305. EPSS is 0.13%. Act only if a listed version of crypto: qat - protect is installed.
Which versions are affected?
Compare what you have installed with Kernel 3.17.0 → 6.6.160; 6.7.0 → 6.12.96; 6.13.0 → 6.18.39. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.13%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Jul 25, 2026 · OpenSSF OSV / OSV Scanner
Detected
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - protect service table iterations with service_lock The service_table list is protected by service_lock when entries are added or removed (in adf_service_add() and adf_service_remove()), but several functions iterate over the list without holding this lock. A concurrent adf_service_register() or adf_service_unregister
Oct 26, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 6.6.160; Kernel fixed in 6.12.96; Kernel fixed in 6.18.39; Kernel fixed in 7.1.4
Oct 26, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 6.6.160; 6.7.0
Oct 26, 2026 · OpenSSF OSV / OSV Scanner
Updated
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - protect service table iterations with service_lock The service_table list is protected by service_lock when entries are added or removed (in adf_service_add() and adf_service_remove()), but several functions iterate over the list without holding this lock. A concurrent adf_service_register() or adf_service_unregister
Sources
- BSI CERT-BundGovernment advisoryCVE-2026-64305
Linux Kernel: Mehrere Schwachstellen
wid.cert-bund.de - CVE.orgVulnerability recordCVE-2026-64305
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-64305
30-day exploitation probability 0.13%
first.org - OpenSSF OSV / OSV ScannerPackage advisoryCVE-2026-64305
crypto: qat - protect service table iterations with service_lock
osv.dev
References
Freshness
Last verified in this catalog Oct 31, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSOct 31, 2026
- BSI CERT-BundOct 27, 2026
- OpenSSF OSV / OSV ScannerOct 26, 2026
- CVE.orgOct 26, 2026