accel/qaic: Address potential out-of-bounds read in resp_worker()
Published Sep 25, 2026
No CVSS score
EPSS 0.16%
Description
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 products
-
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints-
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints-
- Version StatusaffectedConstraints
- Version
-
- Version 6.12.81StatusaffectedConstraints<6.12.111
- Version 6.18.22StatusaffectedConstraints<6.18.53
- Version 6.19.12StatusaffectedConstraints<6.20
- Version 6.6.134StatusaffectedConstraints<6.7
- Version
-
- Version 7.0StatusaffectedConstraints-
- Version 0StatusunaffectedConstraints<7.0
- Version 6.12.111StatusunaffectedConstraints<=6.12.*
- Version 6.18.53StatusunaffectedConstraints<=6.18.*
- Version 7.2.7StatusunaffectedConstraints<=7.2.*
- Version 7.3-rc2StatusunaffectedConstraints<=*
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Linux | Linux | unaffected |
| |||||||||||||||||||||
| Linux | Linux | unaffected |
| |||||||||||||||||||||
| Linux | Linux | affected |
|
No data.
No data.
No Red Hat product state for this CVE.
No package ranges for this CVE.
Remediation
No remediation recorded yet.
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
No CVSS v3.0 score for this CVE.
No CVSS v2.0 score for this CVE.
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
Not enough EPSS history yet for a chart. At least two recorded scores are needed.
Percentile over time
Not enough EPSS history yet for a chart. At least two recorded scores are needed.
No CWE recorded.
References (4)
- https://git.kernel.org/stable/c/12deeade460d47031267256ba07add51cc7eabd0
- https://git.kernel.org/stable/c/ab243f74ab4084ca5c8dec608cb5b0deb27db067
- https://git.kernel.org/stable/c/c72e81ee46bdd4c221114d6e9515e9b4647616d7
- https://git.kernel.org/stable/c/f4b64488f3deca63f7fbc7d7c3835b2e668003f9
Change history (0)
No recorded changes yet.