Linux kernel accel/qaic: unbounded response message walk in resp_worker() reads past the slab allocation
Impact
The QAIC driver's response worker walks a message received from the accelerator device without the bounds checks that decode_message() performs, because an earlier fix for DBC deactivation open-coded the walk. A malformed wire message from the card can push the walk past the end of the slab allocation, spin in an endless loop, or panic the host kernel. On a node with Cloud AI 100 cards this is a host-kernel fault reached from the device side, so the blast radius is the whole node and every tenant workload scheduled on it, not just the process holding the accelerator. Exposure depends on whether anything other than trusted firmware can shape the device's responses - a tenant that can load its own firmware or workload image onto the card is the realistic path. Nodes without QAIC accelerators do not load this driver at all.
Who can reach it
Requires a QAIC (Cloud AI 100) accelerator present and the driver loaded. The malformed input comes from the device, so the attacker must be able to influence what the card sends back - firmware or on-card workload control. No unauthenticated network path.
What to do
Take the stable-kernel fix that makes resp_worker() call decode_message() instead of duplicating the walk; it is in the linked stable commits across the maintained branches. Rolling it out means installing the patched kernel and rebooting each accelerator node, or at minimum unbinding and reloading the qaic module with the card idle - neither is cheap on a node holding running jobs, so drain first. No vendor advisory with fixed version strings is present in the record.
References
Related entries
- Linux drm/amdgpu: BAR0 fallback read path narrowed to SR-IOV VFs onlyCVE-2026-98165 · Linux kernel drm/amdgpu (BAR0 fallback read during early init)Unscored
- Linux drm/ttm: swapped-out resources stay in their bulk_move range, leaving a dangling cursor (use-after-free)CVE-2026-98166 · Linux kernel drm/ttm (bulk_move bookkeeping on buffer-object swapout)Unscored
- Linux drm/amdkfd: integer underflow in the EOP ring size log calculationCVE-2026-98176 · Linux kernel drm/amdkfd (EOP ring size field in cp_hqd_eop_control)Unscored
- Linux drm/amdgpu: NULL dereference during GPU reset when KFD init failed after probeCVE-2026-98178 · Linux kernel drm/amdgpu (amdgpu_amdkfd_clear_kfd_mapping on GPU reset)Unscored
- Linux kernel amdgpu: register BAR mapping leaks on every driver unload or hot-unplugCVE-2026-98179 · Linux kernel amdgpu (register BAR iounmap on device removal)Unscored
- amdgpu nbio_v7_9: NULL dereference in hard IRQ when a RAS interrupt arrives before RAS late_initCVE-2026-98270 · Linux kernel amdgpu nbio_v7_9 (RAS controller interrupt handler)Unscored
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.