<?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 16:30:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-63908 — Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-63908</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: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem&lt;/p&gt;
&lt;p&gt;When a configuration file provides an object size that is larger than the
driver&amp;#39;s known mxt_obj_size(object), the driver intends to discard the
extra bytes.&lt;/p&gt;
&lt;p&gt;The loop iterates using for (i = 0; i &amp;lt; size; i++). Inside the loop, the
condition to skip processing extra bytes is:&lt;/p&gt;
&lt;p&gt;if (i &amp;gt; mxt_obj_size(object))
        continue;&lt;/p&gt;
&lt;p&gt;Since i is a 0-based index, the valid indices for the object are 0 through
mxt_obj_size(object) - 1.&lt;/p&gt;
&lt;p&gt;When i == mxt_obj_size(object), the condition evaluates to false, and the
code processes the byte instead of discarding it.&lt;/p&gt;
&lt;p&gt;This causes the code to calculate byte_offset = reg + i - cfg-&amp;gt;start_ofs
and writes the byte there, overwriting exactly one byte of the adjacent
instance or object.&lt;/p&gt;
&lt;p&gt;Update the boundary check to skip extra bytes correctly by using &amp;gt;=.&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: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem&lt;/p&gt;
&lt;p&gt;When a configuration file provides an object size that is larger than the
driver&amp;#39;s known mxt_obj_size(object), the driver intends to discard the
extra bytes.&lt;/p&gt;
&lt;p&gt;The loop iterates using for (i = 0; i &amp;lt; size; i++). Inside the loop, the
condition to skip processing extra bytes is:&lt;/p&gt;
&lt;p&gt;if (i &amp;gt; mxt_obj_size(object))
        continue;&lt;/p&gt;
&lt;p&gt;Since i is a 0-based index, the valid indices for the object are 0 through
mxt_obj_size(object) - 1.&lt;/p&gt;
&lt;p&gt;When i == mxt_obj_size(object), the condition evaluates to false, and the
code processes the byte instead of discarding it.&lt;/p&gt;
&lt;p&gt;This causes the code to calculate byte_offset = reg + i - cfg-&amp;gt;start_ofs
and writes the byte there, overwriting exactly one byte of the adjacent
instance or object.&lt;/p&gt;
&lt;p&gt;Update the boundary check to skip extra bytes correctly by using &amp;gt;=.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-63908</guid>
    </item>
  </channel>
</rss>
