Answer in brief
CVE-2026-64305 records a High severity (CVSS 7.8) vulnerability in crypto: qat - protect service table iterations with service_lock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d8cba25d2c68992a6e7c1d329b690a9ebe01167d <222fa7b453b612f4407f260146d89a2ce2bc831d || >=d8cba25d2c68992a6e7c1d329b690a9ebe01167d <c3c5925791cff3b84d313293fd60f384d877d793 || >=d8cba25d2c68992a6e7c1d329b690a9ebe01167d <0dbcecea740d943002c1cbdafa39bdfc108e32a5 || >=d8cba25d2c68992a6e7c1d329b690a9ebe01167d <5c6f845e77ec35f9b7b047cc8f9789bf397cdd3e | 222fa7b453b612f4407f260146d89a2ce2bc831d, c3c5925791cff3b84d313293fd60f384d877d793, 0dbcecea740d943002c1cbdafa39bdfc108e32a5, 5c6f845e77ec35f9b7b047cc8f9789bf397cdd3e |
| Linux/Linuxgeneric | 3.17 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.