CVE-2026-64438
crypto: qat - fix VF2PF work teardown race in adf_disable_sriov()
Description
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - fix VF2PF work teardown race in adf_disable_sriov() The VF2PF interrupt handler queues PF-side response work that stores a raw pointer to per-VF state (struct adf_accel_vf_info). Currently, adf_disable_sriov() destroys per-VF mutexes and frees vf_info without stopping new VF2PF work or waiting for in-flight workers to complete. A concurrently scheduled or already queued worker can then dereference freed memory. This manifests as a use-after-free when KASAN is enabled: BUG: KASAN: null-ptr-deref in mutex_lock+0x76/0xe0 Write of size 8 at addr 0000000000000260 by task kworker/24:2/... Workqueue: qat_pf2vf_resp_wq adf_iov_send_resp [intel_qat] Call Trace: kasan_report+0x119/0x140 mutex_lock+0x76/0xe0 adf_gen4_pfvf_send+0xd4/0x1f0 [intel_qat] adf_recv_and_handle_vf2pf_msg+0x290/0x360 [intel_qat] adf_iov_send_resp+0x8c/0xe0 [intel_qat] process_one_work+0x6ac/0xfd0 worker_thread+0x4dd/0xd30 kthread+0x326/0x410 ret_from_fork+0x33b/0x670 Add a PF-local flag, vf2pf_disabled, that gates work queueing, worker processing, and interrupt re-enabling during teardown. Set this flag atomically with the hardware interrupt mask inside adf_disable_all_vf2pf_interrupts(). After masking, synchronize the AE cluster MSI-X interrupt and flush the PF response workqueue before tearing down per-VF locks and state so all in-flight work completes before vf_info is destroyed. Introduce adf_enable_all_vf2pf_interrupts() to clear the flag and unmask all VF2PF interrupts under the same lock when SR-IOV is re-enabled. This ensures the software flag and hardware state transition atomically on both the enable and disable paths.
INFO
Published Date :
July 25, 2026, 10:17 a.m.
Last Modified :
July 25, 2026, 10:17 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64438
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Add a flag to gate work queueing and interrupt handling.
- Mask hardware interrupts before flushing work queues.
- Flush work queues before freeing per-VF state.
- Re-enable interrupts after completing teardown.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64438.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64438 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64438
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64438 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64438 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 25, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'ed8ccaef52fa03fb03cff45b380f72c9f869f273', 'lessThan': '218c2836b3987f3fa1d9eac505462cded0821e4c', 'versionType': 'git'}, {'status': 'affected', 'version': 'ed8ccaef52fa03fb03cff45b380f72c9f869f273', 'lessThan': '446b4d77599cf1a168573f7fb32a4a6aa4f09219', 'versionType': 'git'}, {'status': 'affected', 'version': 'ed8ccaef52fa03fb03cff45b380f72c9f869f273', 'lessThan': '5d916c1eae1933511a69bffe243b4ee5d7da399c', 'versionType': 'git'}, {'status': 'affected', 'version': 'ed8ccaef52fa03fb03cff45b380f72c9f869f273', 'lessThan': 'f344a369d0380d54c8d6c8d24734a78dd5a89817', 'versionType': 'git'}, {'status': 'affected', 'version': 'ed8ccaef52fa03fb03cff45b380f72c9f869f273', 'lessThan': '51144032248cc4ea22917370565650670b8b4e9b', 'versionType': 'git'}, {'status': 'affected', 'version': 'ed8ccaef52fa03fb03cff45b380f72c9f869f273', 'lessThan': '49cd5ac6de8de39a14ead609bb552d372d5602cd', 'versionType': 'git'}, {'status': 'affected', 'version': 'ed8ccaef52fa03fb03cff45b380f72c9f869f273', 'lessThan': '6e92b28cd74fa433658efeadf21b9d4b01023d7d', 'versionType': 'git'}, {'status': 'affected', 'version': 'ed8ccaef52fa03fb03cff45b380f72c9f869f273', 'lessThan': '277281c10c63791067d24d421f7c43a15faa9096', 'versionType': 'git'}], 'programFiles': ['drivers/crypto/intel/qat/qat_common/adf_accel_devices.h', 'drivers/crypto/intel/qat/qat_common/adf_common_drv.h', 'drivers/crypto/intel/qat/qat_common/adf_isr.c', 'drivers/crypto/intel/qat/qat_common/adf_sriov.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '4.3'}, {'status': 'unaffected', 'version': '0', 'lessThan': '4.3', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.261', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.212', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.178', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.145', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.97', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.40', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.4', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/crypto/intel/qat/qat_common/adf_accel_devices.h', 'drivers/crypto/intel/qat/qat_common/adf_common_drv.h', 'drivers/crypto/intel/qat/qat_common/adf_isr.c', 'drivers/crypto/intel/qat/qat_common/adf_sriov.c'], 'defaultStatus': 'affected'}] Added Description In the Linux kernel, the following vulnerability has been resolved: crypto: qat - fix VF2PF work teardown race in adf_disable_sriov() The VF2PF interrupt handler queues PF-side response work that stores a raw pointer to per-VF state (struct adf_accel_vf_info). Currently, adf_disable_sriov() destroys per-VF mutexes and frees vf_info without stopping new VF2PF work or waiting for in-flight workers to complete. A concurrently scheduled or already queued worker can then dereference freed memory. This manifests as a use-after-free when KASAN is enabled: BUG: KASAN: null-ptr-deref in mutex_lock+0x76/0xe0 Write of size 8 at addr 0000000000000260 by task kworker/24:2/... Workqueue: qat_pf2vf_resp_wq adf_iov_send_resp [intel_qat] Call Trace: kasan_report+0x119/0x140 mutex_lock+0x76/0xe0 adf_gen4_pfvf_send+0xd4/0x1f0 [intel_qat] adf_recv_and_handle_vf2pf_msg+0x290/0x360 [intel_qat] adf_iov_send_resp+0x8c/0xe0 [intel_qat] process_one_work+0x6ac/0xfd0 worker_thread+0x4dd/0xd30 kthread+0x326/0x410 ret_from_fork+0x33b/0x670 Add a PF-local flag, vf2pf_disabled, that gates work queueing, worker processing, and interrupt re-enabling during teardown. Set this flag atomically with the hardware interrupt mask inside adf_disable_all_vf2pf_interrupts(). After masking, synchronize the AE cluster MSI-X interrupt and flush the PF response workqueue before tearing down per-VF locks and state so all in-flight work completes before vf_info is destroyed. Introduce adf_enable_all_vf2pf_interrupts() to clear the flag and unmask all VF2PF interrupts under the same lock when SR-IOV is re-enabled. This ensures the software flag and hardware state transition atomically on both the enable and disable paths. Added Reference https://git.kernel.org/stable/c/218c2836b3987f3fa1d9eac505462cded0821e4c Added Reference https://git.kernel.org/stable/c/277281c10c63791067d24d421f7c43a15faa9096 Added Reference https://git.kernel.org/stable/c/446b4d77599cf1a168573f7fb32a4a6aa4f09219 Added Reference https://git.kernel.org/stable/c/49cd5ac6de8de39a14ead609bb552d372d5602cd Added Reference https://git.kernel.org/stable/c/51144032248cc4ea22917370565650670b8b4e9b Added Reference https://git.kernel.org/stable/c/5d916c1eae1933511a69bffe243b4ee5d7da399c Added Reference https://git.kernel.org/stable/c/6e92b28cd74fa433658efeadf21b9d4b01023d7d Added Reference https://git.kernel.org/stable/c/f344a369d0380d54c8d6c8d24734a78dd5a89817