Vulnerability · 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: Ha
Published Sep 25, 2026 · catalog updated Oct 22, 2026 · linux kernel
Check if you run it
No confirmed exploitation is on record for CVE-2026-98155. EPSS is 0.12%. Act only if a listed version of linux kernel is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.1
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.12%
- Remediation
- Version ranges on file
- Affected products
- Ubuntu:16.04:LTS linux-hwe-edge · Ubuntu:18.04:LTS linux-aws-5.0 · Ubuntu:18.04:LTS linux-aws-5.3 · Ubuntu:18.04:LTS linux-azure · Ubuntu:18.04:LTS linux-azure-5.3 · Ubuntu:18.04:LTS linux-azure-edge
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().
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Ubuntu:16.04:LTS linux-hwe-edge4.8.0-28.30~16.04.1, 4.8.0-30.32~16.04.1, 4.8.0-32.34~16.04.1
- Ubuntu:18.04:LTS linux-aws-5.05.0.0-1021.24~18.04.1, 5.0.0-1022.25~18.04.1, 5.0.0-1023.26~18.04.1
- Ubuntu:18.04:LTS linux-aws-5.35.3.0-1016.17~18.04.1, 5.3.0-1017.18~18.04.1, 5.3.0-1019.21~18.04.1
- Ubuntu:18.04:LTS linux-azure4.15.0-1002.2, 4.15.0-1003.3, 4.15.0-1004.4
- Ubuntu:18.04:LTS linux-azure-5.35.3.0-1007.8~18.04.1, 5.3.0-1008.9~18.04.1, 5.3.0-1009.10~18.04.1
- Ubuntu:18.04:LTS linux-azure-edge4.18.0-1006.6~18.04.1, 4.18.0-1007.7~18.04.1, 4.18.0-1008.8~18.04.1
- Ubuntu:18.04:LTS linux-gcp4.15.0-1001.1, 4.15.0-1003.3, 4.15.0-1005.5
- Ubuntu:18.04:LTS linux-gcp-5.35.3.0-1008.9~18.04.1, 5.3.0-1009.10~18.04.1, 5.3.0-1010.11~18.04.1
- Ubuntu:18.04:LTS linux-gke-4.154.15.0-1030.32, 4.15.0-1032.34, 4.15.0-1033.35
- Ubuntu:18.04:LTS linux-gke-5.45.4.0-1025.25~18.04.1, 5.4.0-1027.28~18.04.1, 5.4.0-1029.31~18.04.1
- Ubuntu:18.04:LTS linux-gkeop-5.45.4.0-1001.1, 5.4.0-1003.3, 5.4.0-1004.5
- Ubuntu:18.04:LTS linux-hwe4.18.0-13.14~18.04.1, 4.18.0-14.15~18.04.1, 4.18.0-15.16~18.04.1
- cpe linux/linux kernel7.0
- cpe linux/linux kernel< 6.12.111
- cpe linux/linux kernel< 6.18.53
- cpe linux/linux kernel< 6.20
- cpe linux/linux kernel< 6.6.158
How to fix CVE-2026-98155
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-98155. EPSS is 0.12%. Act only if a listed version of linux kernel is installed.
Which versions are affected?
Compare what you have installed with linux/linux kernel 7.0; linux/linux kernel < 6.12.111; linux/linux kernel < 6.18.53; linux/linux kernel < 6.20. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-125: Out-of-bounds Read. EPSS 0.12%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Sep 25, 2026 · NIST NVD
Detected
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
Oct 20, 2026 · NIST NVD
Updated
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
Oct 22, 2026 · OpenSSF OSV / OSV Scanner
Updated
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
Sources
- CVE.orgVulnerability recordCVE-2026-98155
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-98155
30-day exploitation probability 0.12%
first.org - NIST NVDVulnerability recordCVE-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
nvd.nist.gov - OpenSSF OSV / OSV ScannerPackage advisoryUBUNTU-CVE-2026-98155osv.dev
References
Freshness
Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.