CVE-2026-64305
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.
Affected versions
Linux kernel versions
3.17
and later are affected. Fixed in
6.12.96,
6.18.39,
7.1.4,
7.2-rc1
and their respective stable series.
References
4 totalFrequently asked questions
-
What is CVE-2026-64305?
CVE-2026-64305 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 3.17 onward and has been patched in 6.12.96, 6.18.39, 7.1.4 and others. CVE-2026-64305 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-64305?
Yes. CVE-2026-64305 has been patched. Fixed versions include 6.12.96, 6.18.39, 7.1.4 and others. If you are running Linux kernel 3.17 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-64305 actively exploited?
No. CVE-2026-64305 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.