VulnerabilityPublished 25 Jul 2026Updated 21 Oct 2026

CVE-2026-64305: Linux kernel · crypto: qat – protect service table iterations with service_lock

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in c3c5925791cff3b84d313293fd60f384d877d793 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in c3c5925791cff3b84d313293fd60f384d877d793, 222fa7b453b612f4407f260146d89a2ce2bc831d, 11d48f777cf8fad00db044f4c15cdf821427746b +2

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ d8cba25d2c68992a6e7c1d329b690a9ebe01167d, < c3c5925791cff3b84d313293fd60f384d877d793	Fixed in c3c5925791cff3b84d313293fd60f384d877d793
LinuxLinux	Affected ≥ d8cba25d2c68992a6e7c1d329b690a9ebe01167d, < 222fa7b453b612f4407f260146d89a2ce2bc831d	Fixed in 222fa7b453b612f4407f260146d89a2ce2bc831d
LinuxLinux	Affected ≥ d8cba25d2c68992a6e7c1d329b690a9ebe01167d, < 11d48f777cf8fad00db044f4c15cdf821427746b	Fixed in 11d48f777cf8fad00db044f4c15cdf821427746b
LinuxLinux	Affected ≥ d8cba25d2c68992a6e7c1d329b690a9ebe01167d, < 5c6f845e77ec35f9b7b047cc8f9789bf397cdd3e	Fixed in 5c6f845e77ec35f9b7b047cc8f9789bf397cdd3e
LinuxLinux	Affected ≥ d8cba25d2c68992a6e7c1d329b690a9ebe01167d, < 0dbcecea740d943002c1cbdafa39bdfc108e32a5	Fixed in 0dbcecea740d943002c1cbdafa39bdfc108e32a5
LinuxLinux	Affected =3.17	Fixed in–

Description

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.

References

Community reviews

Loading reviews…