CVE-2026-98155

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

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Potential Mitigations

• Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
• When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
• Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
• To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/540.html

References

• https://git.kernel.org/stable/c/12deeade460d47031267256ba07add51cc7eabd0
• https://git.kernel.org/stable/c/5807a65f301b6c0e73a2dc03dd6f5e80a2861b72
• https://git.kernel.org/stable/c/ab243f74ab4084ca5c8dec608cb5b0deb27db067
• https://git.kernel.org/stable/c/c72e81ee46bdd4c221114d6e9515e9b4647616d7
• https://git.kernel.org/stable/c/f4b64488f3deca63f7fbc7d7c3835b2e668003f9