<?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 21:11:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64271 — Input: touchwin - reset the packet index on every complete packet</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64271</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: touchwin - reset the packet index on every complete packet&lt;/p&gt;
&lt;p&gt;tw_interrupt() accumulates each non-zero serial byte into a fixed
three-byte buffer with a running index that is only reset once a full
packet has been received *and* the device&amp;#39;s two Y bytes agree:&lt;/p&gt;
&lt;p&gt;tw-&amp;gt;data[tw-&amp;gt;idx++] = data;
	if (tw-&amp;gt;idx == TW_LENGTH &amp;amp;&amp;amp; tw-&amp;gt;data[1] == tw-&amp;gt;data[2]) {
		...
		tw-&amp;gt;idx = 0;
	}&lt;/p&gt;
&lt;p&gt;The reset is gated on tw-&amp;gt;data[1] == tw-&amp;gt;data[2], a value the device
controls.  A malicious, malfunctioning or counterfeit Touchwindow
peripheral can stream non-zero bytes whose 2nd and 3rd bytes differ: the
index reaches TW_LENGTH without the equality holding, is never reset, and
keeps growing, so tw-&amp;gt;data[tw-&amp;gt;idx++] walks off the end of the three-byte
array and the rest of the heap-allocated struct tw, one attacker-chosen
byte at a time -- an unbounded, device-driven heap out-of-bounds write.&lt;/p&gt;
&lt;p&gt;Reset the index on every completed packet and report an event only when
the two Y bytes match, like the other serio touchscreen drivers do.&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: touchwin - reset the packet index on every complete packet&lt;/p&gt;
&lt;p&gt;tw_interrupt() accumulates each non-zero serial byte into a fixed
three-byte buffer with a running index that is only reset once a full
packet has been received *and* the device&amp;#39;s two Y bytes agree:&lt;/p&gt;
&lt;p&gt;tw-&amp;gt;data[tw-&amp;gt;idx++] = data;
	if (tw-&amp;gt;idx == TW_LENGTH &amp;amp;&amp;amp; tw-&amp;gt;data[1] == tw-&amp;gt;data[2]) {
		...
		tw-&amp;gt;idx = 0;
	}&lt;/p&gt;
&lt;p&gt;The reset is gated on tw-&amp;gt;data[1] == tw-&amp;gt;data[2], a value the device
controls.  A malicious, malfunctioning or counterfeit Touchwindow
peripheral can stream non-zero bytes whose 2nd and 3rd bytes differ: the
index reaches TW_LENGTH without the equality holding, is never reset, and
keeps growing, so tw-&amp;gt;data[tw-&amp;gt;idx++] walks off the end of the three-byte
array and the rest of the heap-allocated struct tw, one attacker-chosen
byte at a time -- an unbounded, device-driven heap out-of-bounds write.&lt;/p&gt;
&lt;p&gt;Reset the index on every completed packet and report an event only when
the two Y bytes match, like the other serio touchscreen drivers do.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64271</guid>
    </item>
  </channel>
</rss>
