<?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 22:58:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64274 — Input: goodix - clamp the device-reported contact count</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64274</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: goodix - clamp the device-reported contact count&lt;/p&gt;
&lt;p&gt;goodix_ts_read_input_report() copies the number of touch points reported
by the device into an on-stack buffer&lt;/p&gt;
&lt;p&gt;u8 point_data[2 + GOODIX_MAX_CONTACT_SIZE * GOODIX_MAX_CONTACTS];&lt;/p&gt;
&lt;p&gt;which is sized for at most GOODIX_MAX_CONTACTS (10) contacts. The only
runtime check bounds the per-interrupt count against ts-&amp;gt;max_touch_num,
but that value is taken verbatim from a 4-bit field of the device
configuration block and is never clamped:&lt;/p&gt;
&lt;p&gt;ts-&amp;gt;max_touch_num = ts-&amp;gt;config[MAX_CONTACTS_LOC] &amp;amp; 0x0f;&lt;/p&gt;
&lt;p&gt;The nibble can be 0..15, so a malfunctioning, malicious or counterfeit
controller (or an attacker tampering with the I2C bus) can advertise up
to 15 contacts. goodix_ts_read_input_report() then accepts a touch_num
of up to 15 and the second goodix_i2c_read() writes
ts-&amp;gt;contact_size * (touch_num - 1) bytes past the one-contact header into
point_data - up to 30 bytes (45 with the 9-byte report format) beyond the
92-byte buffer: a stack out-of-bounds write.&lt;/p&gt;
&lt;p&gt;Clamp max_touch_num to GOODIX_MAX_CONTACTS, the number of contacts
point_data[] is sized for, when reading it from the configuration.&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: goodix - clamp the device-reported contact count&lt;/p&gt;
&lt;p&gt;goodix_ts_read_input_report() copies the number of touch points reported
by the device into an on-stack buffer&lt;/p&gt;
&lt;p&gt;u8 point_data[2 + GOODIX_MAX_CONTACT_SIZE * GOODIX_MAX_CONTACTS];&lt;/p&gt;
&lt;p&gt;which is sized for at most GOODIX_MAX_CONTACTS (10) contacts. The only
runtime check bounds the per-interrupt count against ts-&amp;gt;max_touch_num,
but that value is taken verbatim from a 4-bit field of the device
configuration block and is never clamped:&lt;/p&gt;
&lt;p&gt;ts-&amp;gt;max_touch_num = ts-&amp;gt;config[MAX_CONTACTS_LOC] &amp;amp; 0x0f;&lt;/p&gt;
&lt;p&gt;The nibble can be 0..15, so a malfunctioning, malicious or counterfeit
controller (or an attacker tampering with the I2C bus) can advertise up
to 15 contacts. goodix_ts_read_input_report() then accepts a touch_num
of up to 15 and the second goodix_i2c_read() writes
ts-&amp;gt;contact_size * (touch_num - 1) bytes past the one-contact header into
point_data - up to 30 bytes (45 with the 9-byte report format) beyond the
92-byte buffer: a stack out-of-bounds write.&lt;/p&gt;
&lt;p&gt;Clamp max_touch_num to GOODIX_MAX_CONTACTS, the number of contacts
point_data[] is sized for, when reading it from the configuration.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64274</guid>
    </item>
  </channel>
</rss>
