CVE-2026-64438

CVE CVE-2026-64438EUVD EUVD-2026-48782Published 2026-07-25T08:51:11.000ZLast changed 2026-08-05T12:42:02.000ZCVSS 8.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 6.1.178; patch: 6.12.97; ed8ccaef52fa03fb03cff45b380f72c9f869f273 <218c2836b3987f3fa1d9eac505462cded0821e4c; ed8ccaef52fa03fb03cff45b380f72c9f869f273 <f344a369d0380d54c8d6c8d24734a78dd5a89817; patch: 5.15.212; ed8ccaef52fa03fb03cff45b380f72c9f869f273 <446b4d77599cf1a168573f7fb32a4a6aa4f09219; ed8ccaef52fa03fb03cff45b380f72c9f869f273 <49cd5ac6de8de39a14ead609bb552d372d5602cd; patch: 6.18.40; ed8ccaef52fa03fb03cff45b380f72c9f869f273 <51144032248cc4ea22917370565650670b8b4e9b; ed8ccaef52fa03fb03cff45b380f72c9f869f273 <277281c10c63791067d24d421f7c43a15faa9096; patch: 5.10.261; ed8ccaef52fa03fb03cff45b380f72c9f869f273 <5d916c1eae1933511a69bffe243b4ee5d7da399c; patch: 6.6.145; patch: 0; patch: 7.2-rc1; ed8ccaef52fa03fb03cff45b380f72c9f869f273 <6e92b28cd74fa433658efeadf21b9d4b01023d7d; 4.3; patch: 7.1.4

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.