CVE-2026-98155: accel/qaic: Address potential out-of-bounds read in resp_worker()
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 12deeade460d47031267256ba07add51cc7eabd0, 5807a65f301b6c0e73a2dc03dd6f5e80a2861b72, 6.12.111; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 12deeade460d47031267256ba07add51cc7eabd0, 5807a65f301b6c0e73a2dc03dd6f5e80a2861b72, 6.12.111; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Sep 25, 2026
- Updated
- Oct 20, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-125
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.6.134 and later · before 6.6.158
- linux linux kernel6.12.81 and later · before 6.12.111
- linux linux kernel6.18.22 and later · before 6.18.53
- linux linux kernel6.19.12 and later · before 6.20
- linux linux kernel7.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- ee0180e77e6c8482644569632065411de844c515, 7.0affected
- 2dd67966f39a2abf8ccb4865031c722e40e01b7f and later · before 5807a65f301b6c0e73a2dc03dd6f5e80a2861b72affected · git
- 08021f2d4a557d6491e3bcc288e96425f50aa3cf and later · before f4b64488f3deca63f7fbc7d7c3835b2e668003f9affected · git
- f403094d9075d7c565a3d81002b781c325cb3c07 and later · before 12deeade460d47031267256ba07add51cc7eabd0affected · git
- 2feec5ae5df785658924ab6bd91280dc3926507c and later · before c72e81ee46bdd4c221114d6e9515e9b4647616d7affected · git
- 2feec5ae5df785658924ab6bd91280dc3926507c and later · before ab243f74ab4084ca5c8dec608cb5b0deb27db067affected · git
- 6.6.134 and later · before 6.6.158affected · semver
- 6.12.81 and later · before 6.12.111affected · semver
- 6.18.22 and later · before 6.18.53affected · semver
- 6.19.12 and later · before 6.20affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-98153Sep 25, 2026 · nvme: fix racy access to FDP placement id array22Monitor
- ← EarlierCVE-2026-98154Sep 25, 2026 · nvme-rdma: fix -EIO cleanup order in queue_rq28Monitor
- Later →CVE-2026-98156Sep 25, 2026 · drm/virtio: use the DMA API for resource backing on Xen31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 12deeade460d47031267256ba07add51cc7eabd0 | Vendor (CNA) |
| Linux Linux | 5807a65f301b6c0e73a2dc03dd6f5e80a2861b72 | Vendor (CNA) |
| Linux Linux | 6.12.111 | Vendor (CNA) |
| Linux Linux | 6.18.53 | Vendor (CNA) |
| Linux Linux | 6.20 | Vendor (CNA) |
| Linux Linux | 6.6.158 | Vendor (CNA) |
| Linux Linux | ab243f74ab4084ca5c8dec608cb5b0deb27db067 | Vendor (CNA) |
| Linux Linux | c72e81ee46bdd4c221114d6e9515e9b4647616d7 | Vendor (CNA) |
| Linux Linux | f4b64488f3deca63f7fbc7d7c3835b2e668003f9 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1184 · Sep 28, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- CVSS— → 7.1
- Severity— → high
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.