Database/Kernel, userspace & hypervisor
Linux kernel Intel QAT: unlocked service_table walks can corrupt the list or use freed entries
Impact
The QAT driver's service_table list is protected by service_lock on add and remove, but adf_dev_init(), adf_dev_start(), adf_dev_stop(), adf_dev_shutdown(), the restart notifiers and adf_error_notifier() all walked it without holding that lock. A service registering or unregistering while one of those runs can corrupt the list or leave a walker dereferencing a freed entry, which on a server means a host panic during device bring-up, teardown or error recovery. This is relevant to fleets running Intel QuickAssist offload - built into recent Xeon Scalable parts and commonly surfaced to workloads through the QAT device plugin - where a crash takes the node and every GPU job on it. Be clear about reachability: both sides of the race are privileged operations (loading or unloading a QAT service module, or bringing a device up and down), so an unprivileged tenant pod cannot drive this. The vendor-supplied 7.8 local score assumes a local attacker who already holds those privileges; treat this as a stability fix for nodes that expose QAT rather than a tenant-escape.
Who can reach it
Local and privileged: something able to load or unload a QAT service module, or to start/stop a QAT device, concurrently with another CPU walking the service table. Not reachable from an unprivileged container or a tenant holding only an accelerator device node.
What to do
Pick up a stable kernel containing the listed commits and reboot each node that has QAT devices bound; the change is inside the driver, so there is no sysfs or module-parameter mitigation. Until then, avoid loading or unloading QAT service modules while devices are being brought up or torn down, and do not script QAT module reloads into node bring-up automation. Nodes with QAT disabled in BIOS or with the driver unloaded are unaffected.
References
Related entries
- Linux kernel BPF: LPM trie RCU annotations reject sleepable programs and spam lockdep warningsCVE-2026-64352 · Linux kernel BPF LPM trie (RCU annotations for sleepable programs)High
- Linux BPF: BTF repeated-field count overflow allows an out-of-bounds write on BPF_BTF_LOADCVE-2026-64354 · Linux kernel BPF BTF parser (btf_repeat_fields expansion)High
- Linux mm: shrinker_info teardown races with expansion, giving a double free of memcg shrinker mapsCVE-2026-64418 · Linux kernel memcg shrinker_info (alloc/teardown race with expand_shrinker_info)High
- Linux kernel perf/core: remove_on_exec leaves stale group state, corrupting the PMU active listCVE-2026-64556 · Linux kernel perf/core (perf_event_remove_on_exec group detach)High
- Linux kernel BPF TCP iterator: double socket release on batch realloc failure panics the nodeCVE-2026-64575 · Linux kernel BPF TCP iterator (bpf_iter_tcp_batch)High
- Linux kernel (net/xfrm): Setting a per-socket IPsec policy reset the socket's destination cache non-atomically whileCVE-2026-64581 · Linux kernel (net/xfrm)High
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.