<?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>Tue, 29 Sep 2026 23:45:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80570 — Input: synaptics-rmi4 - zero report size on F54 work error</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80570</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;Input: synaptics-rmi4 - zero report size on F54 work error&lt;/p&gt;
&lt;p&gt;In rmi_f54_work(), if an error occurs during report request or command
verification, the code jumped directly to the &amp;#39;error&amp;#39; label, bypassing
the &amp;#39;abort&amp;#39; label where f54-&amp;gt;report_size was normally zeroed out.&lt;/p&gt;
&lt;p&gt;This left f54-&amp;gt;report_size containing its previous successful payload
size. If a user then altered the V4L2 format to a smaller size, and a
subsequent run failed, rmi_f54_buffer_queue() would copy the stale,
larger payload size into the shrunken V4L2 buffer, causing a heap
buffer overflow.&lt;/p&gt;
&lt;p&gt;Fix this by merging the &amp;#39;abort&amp;#39; and &amp;#39;error&amp;#39; labels into a single &amp;#39;out&amp;#39;
exit path, and ensuring that f54-&amp;gt;report_size is always set to 0 on
failure by checking for error and zeroing the local report_size first.&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;Input: synaptics-rmi4 - zero report size on F54 work error&lt;/p&gt;
&lt;p&gt;In rmi_f54_work(), if an error occurs during report request or command
verification, the code jumped directly to the &amp;#39;error&amp;#39; label, bypassing
the &amp;#39;abort&amp;#39; label where f54-&amp;gt;report_size was normally zeroed out.&lt;/p&gt;
&lt;p&gt;This left f54-&amp;gt;report_size containing its previous successful payload
size. If a user then altered the V4L2 format to a smaller size, and a
subsequent run failed, rmi_f54_buffer_queue() would copy the stale,
larger payload size into the shrunken V4L2 buffer, causing a heap
buffer overflow.&lt;/p&gt;
&lt;p&gt;Fix this by merging the &amp;#39;abort&amp;#39; and &amp;#39;error&amp;#39; labels into a single &amp;#39;out&amp;#39;
exit path, and ensuring that f54-&amp;gt;report_size is always set to 0 on
failure by checking for error and zeroing the local report_size first.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80570</guid>
    </item>
  </channel>
</rss>
