CVE-2026-64438: crypto: qat - fix VF2PF work teardown race in adf_disable_sriov()
Noroxi assessment
Priority: Monitor (action score 35/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.13% (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 218c2836b3987f3fa1d9eac505462cded0821e4c, 277281c10c63791067d24d421f7c43a15faa9096, 446b4d77599cf1a168573f7fb32a4a6aa4f09219.
Low priority for now. Upgrade to Linux Linux 218c2836b3987f3fa1d9eac505462cded0821e4c, 277281c10c63791067d24d421f7c43a15faa9096, 446b4d77599cf1a168573f7fb32a4a6aa4f09219 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 - 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.
- Published
- Jul 25, 2026
- Updated
- Oct 24, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-416
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
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 helpAffected 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 kernel4.3 and later · before 5.10.261
- linux linux kernel5.11 and later · before 5.15.212
- linux linux kernel5.16 and later · before 6.1.178
- linux linux kernel6.2 and later · before 6.6.145
- linux linux kernel6.7 and later · before 6.12.97
- linux linux kernel6.13 and later · before 6.18.40
- 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
- 4.3affected
- ed8ccaef52fa03fb03cff45b380f72c9f869f273 and later · before 218c2836b3987f3fa1d9eac505462cded0821e4caffected · git
- ed8ccaef52fa03fb03cff45b380f72c9f869f273 and later · before 446b4d77599cf1a168573f7fb32a4a6aa4f09219affected · git
- ed8ccaef52fa03fb03cff45b380f72c9f869f273 and later · before 5d916c1eae1933511a69bffe243b4ee5d7da399caffected · git
- ed8ccaef52fa03fb03cff45b380f72c9f869f273 and later · before f344a369d0380d54c8d6c8d24734a78dd5a89817affected · git
- ed8ccaef52fa03fb03cff45b380f72c9f869f273 and later · before 51144032248cc4ea22917370565650670b8b4e9baffected · git
- ed8ccaef52fa03fb03cff45b380f72c9f869f273 and later · before 49cd5ac6de8de39a14ead609bb552d372d5602cdaffected · git
- ed8ccaef52fa03fb03cff45b380f72c9f869f273 and later · before 6e92b28cd74fa433658efeadf21b9d4b01023d7daffected · git
- ed8ccaef52fa03fb03cff45b380f72c9f869f273 and later · before 277281c10c63791067d24d421f7c43a15faa9096affected · git
- before 4.3not 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 | before 6.1.180-1 | 6.1.180-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
| Red Hat:enterprise_linux_eus:10.0 | kernel | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-core | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-debug | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-debug-core | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-debug-debuginfo | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-debug-devel | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-debug-devel-matched | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-debug-modules | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-debug-modules-core | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-debug-modules-extra | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-debuginfo | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-devel | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-devel-matched | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-modules | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-modules-core | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-64k-modules-extra | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-abi-stablelists | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-core | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
| Red Hat:enterprise_linux_eus:10.0 | kernel-debug | before 0:6.12.0-55.108.1.el10_0 | 0:6.12.0-55.108.1.el10_0 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64435Jul 25, 2026 · audit: Fix data races of skb_queue_len() readers on audit_queue32Monitor
- ← EarlierCVE-2026-64436Jul 25, 2026 · net: af_key: initialize alg_key_len for IPComp states28Monitor
- Later →CVE-2026-64439Jul 25, 2026 · crypto: krb5 - filter out async aead implementations at alloc39Monitor
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 | 218c2836b3987f3fa1d9eac505462cded0821e4c | Vendor (CNA) |
| Linux Linux | 277281c10c63791067d24d421f7c43a15faa9096 | Vendor (CNA) |
| Linux Linux | 446b4d77599cf1a168573f7fb32a4a6aa4f09219 | Vendor (CNA) |
| Linux Linux | 49cd5ac6de8de39a14ead609bb552d372d5602cd | Vendor (CNA) |
| Linux Linux | 51144032248cc4ea22917370565650670b8b4e9b | Vendor (CNA) |
| Linux Linux | 5d916c1eae1933511a69bffe243b4ee5d7da399c | Vendor (CNA) |
| Linux Linux | 6e92b28cd74fa433658efeadf21b9d4b01023d7d | Vendor (CNA) |
| Linux Linux | f344a369d0380d54c8d6c8d24734a78dd5a89817 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-570.141.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-570.141.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-570.141.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-570.141.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-570.141.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-570.141.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-570.141.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-570.141.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-570.141.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-570.141.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-570.141.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-570.141.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | 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.
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 researchersFinders, 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
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
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 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&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— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/277281c10c63791067d24d421f7c43a15faa9096
- git.kernel.org/stable/c/446b4d77599cf1a168573f7fb32a4a6aa4f09219
- git.kernel.org/stable/c/49cd5ac6de8de39a14ead609bb552d372d5602cd
- git.kernel.org/stable/c/51144032248cc4ea22917370565650670b8b4e9b
- git.kernel.org/stable/c/5d916c1eae1933511a69bffe243b4ee5d7da399c
- git.kernel.org/stable/c/6e92b28cd74fa433658efeadf21b9d4b01023d7d
- git.kernel.org/stable/c/f344a369d0380d54c8d6c8d24734a78dd5a89817
Vendor advisories and official records. Exploit/PoC links are deliberately left out.