NVD / CVE Program· CNA Linux

CVE-2026-64305: crypto: qat - protect service table iterations with service_lock

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 0dbcecea740d943002c1cbdafa39bdfc108e32a5, 11d48f777cf8fad00db044f4c15cdf821427746b, 222fa7b453b612f4407f260146d89a2ce2bc831d.

Low priority for now. Upgrade to Linux Linux 0dbcecea740d943002c1cbdafa39bdfc108e32a5, 11d48f777cf8fad00db044f4c15cdf821427746b, 222fa7b453b612f4407f260146d89a2ce2bc831d or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

Published: Jul 25, 2026
Updated: Nov 6, 2026
EPSS: 0.1% · 2th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel3.17 and later · before 6.12.96
linux linux kernel6.13 and later · before 6.18.39
linux linux kernel6.19 and later · before 7.1.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 3.17affected
- d8cba25d2c68992a6e7c1d329b690a9ebe01167d and later · before d36bff434e01d06d1e1fa98aa2b34ec32185c1abaffected · git
- d8cba25d2c68992a6e7c1d329b690a9ebe01167d and later · before 11d48f777cf8fad00db044f4c15cdf821427746baffected · git
- d8cba25d2c68992a6e7c1d329b690a9ebe01167d and later · before 222fa7b453b612f4407f260146d89a2ce2bc831daffected · git
- d8cba25d2c68992a6e7c1d329b690a9ebe01167d and later · before c3c5925791cff3b84d313293fd60f384d877d793affected · git
- d8cba25d2c68992a6e7c1d329b690a9ebe01167d and later · before 0dbcecea740d943002c1cbdafa39bdfc108e32a5affected · git
- d8cba25d2c68992a6e7c1d329b690a9ebe01167d and later · before 5c6f845e77ec35f9b7b047cc8f9789bf397cdd3eaffected · git
- before 3.17not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	from 0	—
Debian:12	linux-6.12	before 6.12.100-1~deb12u1	6.12.100-1~deb12u1
Debian:13	linux	before 6.12.96-1	6.12.96-1
Debian:14	linux	before 7.1.4-1	7.1.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2026-64303Jul 25, 2026 · spi: fsl-lpspi: terminate the RX channel on TX prepare failure path
39Monitor
← EarlierCVE-2026-64304Jul 25, 2026 · crypto: qat - validate RSA CRT component lengths
31Monitor
Later →CVE-2026-64306Jul 25, 2026 · crypto: drbg - Fix returning success on failure in CTR_DRBG
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	0dbcecea740d943002c1cbdafa39bdfc108e32a5	Vendor (CNA)
Linux Linux	11d48f777cf8fad00db044f4c15cdf821427746b	Vendor (CNA)
Linux Linux	222fa7b453b612f4407f260146d89a2ce2bc831d	Vendor (CNA)
Linux Linux	5c6f845e77ec35f9b7b047cc8f9789bf397cdd3e	Vendor (CNA)
Linux Linux	c3c5925791cff3b84d313293fd60f384d877d793	Vendor (CNA)
Linux Linux	d36bff434e01d06d1e1fa98aa2b34ec32185c1ab	Vendor (CNA)
debian:linux	6.12.96-1 · Debian:13	Package registry (OSV)
debian:linux-6.12	6.12.100-1~deb12u1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

SSVC exploitation— → noneNov 6, 2026, 6:07 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/0dbcecea740d943002c1cbdafa39bdfc108e32a5

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records