Linux vulnerability

What happened

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().

Affected versions

Linux: 2dd67966f39a2abf8ccb4865031c722e40e01b7f through before 5807a65f301b6c0e73a2dc03dd6f5e80a2861b72 (git); 08021f2d4a557d6491e3bcc288e96425f50aa3cf through before f4b64488f3deca63f7fbc7d7c3835b2e668003f9 (git); f403094d9075d7c565a3d81002b781c325cb3c07 through before 12deeade460d47031267256ba07add51cc7eabd0 (git); 2feec5ae5df785658924ab6bd91280dc3926507c through before c72e81ee46bdd4c221114d6e9515e9b4647616d7 (git); 2feec5ae5df785658924ab6bd91280dc3926507c through before ab243f74ab4084ca5c8dec608cb5b0deb27db067 (git); ee0180e77e6c8482644569632065411de844c515 (git); 6.6.134 through before 6.6.158 (semver); 6.12.81 through before 6.12.111 (semver); 6.18.22 through before 6.18.53 (semver); 6.19.12 through before 6.20 (semver); 7.0 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

• Apply vendor-provided updates or mitigations.
• Review affected product exposure and access logs.