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.
Published: 2026-07-25
Score: 7.0 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The QAT crypto driver in the Linux kernel protects the service_table list only when adding or removing entries. Several functions iterate over this list without holding the service_lock, allowing a concurrent adf_service_register or adf_service_unregister to modify the list during traversal. This race can corrupt the linked list or trigger a use‑after‑free, resulting in kernel memory corruption. Such corruption might crash the kernel or, in a worst‑case scenario, provide a vehicle for arbitrary kernel code execution.

Affected Systems

The vulnerability is present in the Linux kernel’s QAT crypto driver. No specific kernel version range is provided, so any kernel that includes the unpatched QAT code before the fix is potentially affected.

Risk and Exploitability

The CVSS score of 7.0 gives the vulnerability a high severity classification. The EPSS score is less than 1%, indicating a low likelihood of exploitation in the wild. The issue is not listed in CISA's KEV catalog. Exploitation would require an attacker to trigger concurrent service registration and unregistration, which likely demands local privileged access or the ability to execute code that interacts with the QAT subsystem. Due to these constraints, the attack vector is presumably local, but the exact access requirements are not fully specified in the advisory.

Generated by OpenCVE AI on August 4, 2026 at 14:46 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply a kernel update that contains the QAT driver patch.
  • If a kernel upgrade is not immediately possible, disable or unload the QAT crypto module to prevent the vulnerable code from running.
  • Monitor system logs and kernel crash reports for signs of list corruption or kernel panics, and apply the patch as soon as it becomes available.

Generated by OpenCVE AI on August 4, 2026 at 14:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4724-1 linux-6.12 new package
History

Mon, 03 Aug 2026 19:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362
CWE-416

Thu, 30 Jul 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-366
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Moderate


Sun, 26 Jul 2026 02:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362
CWE-416

Sat, 25 Jul 2026 09:30:00 +0000

Type Values Removed Values Added
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.
Title crypto: qat - protect service table iterations with service_lock
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-07-25T08:49:39.536Z

Reserved: 2026-07-19T15:36:31.779Z

Link: CVE-2026-64305

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-07-25T10:17:11.530

Modified: 2026-08-11T15:00:57.447

Link: CVE-2026-64305

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-07-25T00:00:00Z

Links: CVE-2026-64305 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-04T15:00:13Z

Weaknesses
  • CWE-366

    Race Condition within a Thread