Skip to main content
No exploitation reportedFix available

CVE-2026-98155

No exploitation reported by the sources we read.

  • Published2026-09-25
  • Fixed in6.20 · 6.18.53 · 6.12.111 · 6.6.158
  • WeaknessCWE-125

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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

Timeline

dates in UTC
  1. 2026-09-2511:17CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-98155?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-98155?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Linux linux kernel
BranchAffectedFixed in
6.x≥ 6.19.12, < 6.206.20
6.18≥ 6.18.22, < 6.18.536.18.53
6.12≥ 6.12.81, < 6.12.1116.12.111
6.6≥ 6.6.134, < 6.6.1586.6.158
7.0= 7.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2026-98155 Red Hat Product Security77 known affected

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

    kernel as a component of Red Hat Enterprise Linux 10 · kernel-64k as a component of Red Hat Enterprise Linux 10 · kernel-64k-core as a component of Red Hat Enterprise Linux 10 · +74 more

Full record on NVD

Fix

  1. Update Linux linux kernel to 6.20 · 6.18.53 · 6.12.111 · 6.6.158
  2. Workaround from the vendor Red Hat Product Security CVE-2026-98155 · 77 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
  3. No fix available, says the vendor Red Hat Product Security CVE-2026-98155 · 77 productsFix deferred

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.17.1read 2026-10-23
  • NVDweakness (CWE)CWE-125read 2026-10-23
  • FIRST EPSSEPSS score0.1 %2026-10-22

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Published
2026-09-25
Last Modified
2026-10-20
NVD status
Analyzed

Frequently asked questions

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

Is CVE-2026-98155 actively exploited?

Active exploitation of CVE-2026-98155 has not been confirmed. Its EPSS score was 0.1% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-98155?

CVE-2026-98155 has a CVSS v3 base score of 7.1 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database