<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T06:56:58.851002+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-80570</id>
    <title>CVE-2026-80570 — Input: synaptics-rmi4 - zero report size on F54 work error</title>
    <updated>2026-09-30T06:56:58.872545+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>Input: synaptics-rmi4 - zero report size on F54 work error</p>
<p>In rmi_f54_work(), if an error occurs during report request or command
verification, the code jumped directly to the 'error' label, bypassing
the 'abort' label where f54-&gt;report_size was normally zeroed out.</p>
<p>This left f54-&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.</p>
<p>Fix this by merging the 'abort' and 'error' labels into a single 'out'
exit path, and ensuring that f54-&gt;report_size is always set to 0 on
failure by checking for error and zeroing the local report_size first.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-80570"/>
  </entry>
</feed>
