accel/qaic: Address potential out-of-bounds read in resp_worker() (CVE-2026-98155) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-98155

accel/qaic: Address potential out-of-bounds read in resp_worker()

Answer in brief

CVE-2026-98155 records a Unknown severity vulnerability in accel/qaic: Address potential out-of-bounds read in resp_worker(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 25, 2026Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=08021f2d4a557d6491e3bcc288e96425f50aa3cf <f4b64488f3deca63f7fbc7d7c3835b2e668003f9 \|\| >=f403094d9075d7c565a3d81002b781c325cb3c07 <12deeade460d47031267256ba07add51cc7eabd0 \|\| >=2feec5ae5df785658924ab6bd91280dc3926507c <c72e81ee46bdd4c221114d6e9515e9b4647616d7 \|\| >=2feec5ae5df785658924ab6bd91280dc3926507c <ab243f74ab4084ca5c8dec608cb5b0deb27db067 \|\| 2dd67966f39a2abf8ccb4865031c722e40e01b7f \|\| ee0180e77e6c8482644569632065411de844c515 \|\| >=6.12.81 <6.12.111 \|\| >=6.18.22 <6.18.53 \|\| >=6.6.134 <6.7 \|\| >=6.19.12 <6.20	f4b64488f3deca63f7fbc7d7c3835b2e668003f9, 12deeade460d47031267256ba07add51cc7eabd0, c72e81ee46bdd4c221114d6e9515e9b4647616d7, ab243f74ab4084ca5c8dec608cb5b0deb27db067, 6.12.111, 6.18.53, 6.7, 6.20
Linux/Linuxgeneric	7.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to f4b64488f3deca63f7fbc7d7c3835b2e668003f9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source description

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

Quoted source text, attributed separately from HOL analysis.