accel/qaic: Address potential out-of-bounds read in resp_worker()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
ee0180e77e6c8482644569632065411de844c515| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
accel/qaic: Address potential out-of-bounds read in resp_worker()
Although 'commit 2feec5ae5df7 ("accel/qaic: Handle DBC deactivation if the owner went away")' fixes the scenario it was intended for by walking the message and only decoding QAIC_TRANS_DEACTIVATE_FROM_DEV, if present, it skipped over the bounds checking code that is included in decode_message(). This could lead to issues such as reading past the slab allocation's end, infinite loops or kernel panics. For those issues to happen, a malformed wire message is needed to be sent from the device.
Instead of duplicating the bounds checking code already present in decode_message(), use the function inside resp_worker().
From the CVE record · Linux
The Linux kernel's accel/qaic resp_worker() can skip bounds checks when processing a device message. A malformed wire message from the device could cause an out-of-bounds read, an infinite loop, or a kernel panic. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with the accel/qaic driver should check their exposure; affected versions are not specified.