<?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>Thu, 01 Oct 2026 02:13:16 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64271</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-64271</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-64271</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0982 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-0982</link>
      <description>certfr-2026-avi-0982</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-0982</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64271</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-64271</link>
      <description>&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;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/fkie_cve-2026-64271</guid>
    </item>
    <item>
      <title>GHSA-v33c-vvwm-9mr7</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-v33c-vvwm-9mr7</link>
      <description>&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;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/ghsa-v33c-vvwm-9mr7</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-64271 — Input: touchwin - reset the packet index on every complete packet</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-64271</link>
      <description>msrc_CVE-2026-64271</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-64271</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11476-1 — kernel-devel-7.1.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1</link>
      <description>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23477-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2026:23477-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/suse-su-2026:23477-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64271</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64271</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Input: touchwin - reset the packet index on every complete packet 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: 	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; 	} 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. 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; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Input: touchwin - reset the packet index on every complete packet 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: 	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; 	} 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. 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/ubuntu-cve-2026-64271</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2527 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527</guid>
    </item>
  </channel>
</rss>
