<?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 01:24:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64276 — Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64276</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 - bound the F30 keymap to the GPIO/LED count&lt;/p&gt;
&lt;p&gt;rmi_f30_map_gpios() allocates gpioled_key_map with
min(gpioled_count, TRACKSTICK_RANGE_END) == at most 6 entries, but
rmi_f30_attention() iterates the full f30-&amp;gt;gpioled_count (device query
register, range 0..31) and dereferences gpioled_key_map[i], and
input-&amp;gt;keycodemax is set to the full gpioled_count while input-&amp;gt;keycode
points at the 6-entry allocation.&lt;/p&gt;
&lt;p&gt;A device that reports gpioled_count &amp;gt; 6 with GPIO support enabled
therefore causes an out-of-bounds read on the attention interrupt and
out-of-bounds read/write through the EVIOCGKEYCODE/EVIOCSKEYCODE ioctls,
which bound the index only against keycodemax. This is the same defect
as the F3A handler, which was copied from F30.&lt;/p&gt;
&lt;p&gt;Size the keymap for the full gpioled_count; the mapping loop still
assigns only the first min(gpioled_count, TRACKSTICK_RANGE_END) entries.&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 - bound the F30 keymap to the GPIO/LED count&lt;/p&gt;
&lt;p&gt;rmi_f30_map_gpios() allocates gpioled_key_map with
min(gpioled_count, TRACKSTICK_RANGE_END) == at most 6 entries, but
rmi_f30_attention() iterates the full f30-&amp;gt;gpioled_count (device query
register, range 0..31) and dereferences gpioled_key_map[i], and
input-&amp;gt;keycodemax is set to the full gpioled_count while input-&amp;gt;keycode
points at the 6-entry allocation.&lt;/p&gt;
&lt;p&gt;A device that reports gpioled_count &amp;gt; 6 with GPIO support enabled
therefore causes an out-of-bounds read on the attention interrupt and
out-of-bounds read/write through the EVIOCGKEYCODE/EVIOCSKEYCODE ioctls,
which bound the index only against keycodemax. This is the same defect
as the F3A handler, which was copied from F30.&lt;/p&gt;
&lt;p&gt;Size the keymap for the full gpioled_count; the mapping loop still
assigns only the first min(gpioled_count, TRACKSTICK_RANGE_END) entries.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64276</guid>
    </item>
  </channel>
</rss>
