<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 17:32:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98155 — accel/qaic: Address potential out-of-bounds read in resp_worker()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-98155</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;accel/qaic: Address potential out-of-bounds read in resp_worker()&lt;/p&gt;
&lt;p&gt;Although &amp;#39;commit 2feec5ae5df7 (&amp;#34;accel/qaic: Handle DBC deactivation if the
owner went away&amp;#34;)&amp;#39; 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&amp;#39;s end,
infinite loops or kernel panics. For those issues to happen, a malformed
wire message is needed to be sent from the device.&lt;/p&gt;
&lt;p&gt;Instead of duplicating the bounds checking code already present in
decode_message(), use the function inside resp_worker().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;accel/qaic: Address potential out-of-bounds read in resp_worker()&lt;/p&gt;
&lt;p&gt;Although &amp;#39;commit 2feec5ae5df7 (&amp;#34;accel/qaic: Handle DBC deactivation if the
owner went away&amp;#34;)&amp;#39; 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&amp;#39;s end,
infinite loops or kernel panics. For those issues to happen, a malformed
wire message is needed to be sent from the device.&lt;/p&gt;
&lt;p&gt;Instead of duplicating the bounds checking code already present in
decode_message(), use the function inside resp_worker().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-98155</guid>
    </item>
  </channel>
</rss>
