<?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>Fri, 02 Oct 2026 21:42:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72089 — accel/ivpu: Reject firmware log with size smaller than header</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72089</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/ivpu: Reject firmware log with size smaller than header&lt;/p&gt;
&lt;p&gt;fw_log_from_bo() validates the tracing buffer header_size and that the
log fits within the BO, but never checks that log-&amp;gt;size is at least
log-&amp;gt;header_size. fw_log_print_buffer() then computes:&lt;/p&gt;
&lt;p&gt;u32 data_size = log-&amp;gt;size - log-&amp;gt;header_size;&lt;/p&gt;
&lt;p&gt;which underflows to a near-U32_MAX value when firmware reports a log whose
size is smaller than its header. That huge data_size defeats the
log_start/log_end bounds clamps added by commit dd1311bcf0e6 (&amp;#34;accel/ivpu:
Add bounds checks for firmware log indices&amp;#34;), so fw_log_print_lines() reads
far past the small real data region of the BO. A size of 0 also makes
fw_log_from_bo() advance the offset by 0, causing the callers to loop
forever on the same header.&lt;/p&gt;
&lt;p&gt;Reject logs whose size is smaller than the header (which also rejects
size == 0).&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/ivpu: Reject firmware log with size smaller than header&lt;/p&gt;
&lt;p&gt;fw_log_from_bo() validates the tracing buffer header_size and that the
log fits within the BO, but never checks that log-&amp;gt;size is at least
log-&amp;gt;header_size. fw_log_print_buffer() then computes:&lt;/p&gt;
&lt;p&gt;u32 data_size = log-&amp;gt;size - log-&amp;gt;header_size;&lt;/p&gt;
&lt;p&gt;which underflows to a near-U32_MAX value when firmware reports a log whose
size is smaller than its header. That huge data_size defeats the
log_start/log_end bounds clamps added by commit dd1311bcf0e6 (&amp;#34;accel/ivpu:
Add bounds checks for firmware log indices&amp;#34;), so fw_log_print_lines() reads
far past the small real data region of the BO. A size of 0 also makes
fw_log_from_bo() advance the offset by 0, causing the callers to loop
forever on the same header.&lt;/p&gt;
&lt;p&gt;Reject logs whose size is smaller than the header (which also rejects
size == 0).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72089</guid>
    </item>
  </channel>
</rss>
