CyberSecBulletin
CVE-2026-98155NVD status: Analyzed

Linux: Out-of-bounds Read

Published Updated By the CyberSecBulletin desk

CVE-2026-98155 is a high-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 5807a65f301b6c0e73a2dc03dd6f5e80a2861b72, f4b64488f3deca63f7fbc7d7c3835b2e668003f9, 12deeade460d47031267256ba07add51cc7eabd0 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.12% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 5807a65f301b6c0e73a2dc03dd6f5e80a2861b72 or f4b64488f3deca63f7fbc7d7c3835b2e668003f9 or 12deeade460d47031267256ba07add51cc7eabd0 or c72e81ee46bdd4c221114d6e9515e9b4647616d7, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.158 or 6.12.111 or 6.18.53 or 6.20, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux2dd67966f39a2abf8ccb4865031c722e40e01b7f up to, but not including, 5807a65f301b6c0e73a2dc03dd6f5e80a2861b72; 08021f2d4a557d6491e3bcc288e96425f50aa3cf up to, but not including, f4b64488f3deca63f7fbc7d7c3835b2e668003f9; f403094d9075d7c565a3d81002b781c325cb3c07 up to, but not including, 12deeade460d47031267256ba07add51cc7eabd0; 2feec5ae5df785658924ab6bd91280dc3926507c up to, but not including, c72e81ee46bdd4c221114d6e9515e9b4647616d7; 2feec5ae5df785658924ab6bd91280dc3926507c up to, but not including, ab243f74ab4084ca5c8dec608cb5b0deb27db067; ee0180e77e6c8482644569632065411de844c515; 6.6.134 up to, but not including, 6.6.158; 6.12.81 up to, but not including, 6.12.111; and 3 more ranges5807a65f301b6c0e73a2dc03dd6f5e80a2861b72, f4b64488f3deca63f7fbc7d7c3835b2e668003f9, 12deeade460d47031267256ba07add51cc7eabd0, c72e81ee46bdd4c221114d6e9515e9b4647616d7, ab243f74ab4084ca5c8dec608cb5b0deb27db067, 6.6.158
LinuxLinux Kernel6.6.134 up to, but not including, 6.6.158; 6.12.81 up to, but not including, 6.12.111; 6.18.22 up to, but not including, 6.18.53; 6.19.12 up to, but not including, 6.20; 7.06.6.158, 6.12.111, 6.18.53, 6.20

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.

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

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Read

The product reads data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that provides appropriate memory abstractions.

More Out-of-bounds Read vulnerabilities (CWE-125)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Read vulnerabilities

Spotted an error? Tell us.