<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T16:31:16.989167+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-63908</id>
    <title>CVE-2026-63908 — Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem</title>
    <updated>2026-10-01T16:31:16.990785+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem</p>
<p>When a configuration file provides an object size that is larger than the
driver's known mxt_obj_size(object), the driver intends to discard the
extra bytes.</p>
<p>The loop iterates using for (i = 0; i &lt; size; i++). Inside the loop, the
condition to skip processing extra bytes is:</p>
<p>if (i &gt; mxt_obj_size(object))
        continue;</p>
<p>Since i is a 0-based index, the valid indices for the object are 0 through
mxt_obj_size(object) - 1.</p>
<p>When i == mxt_obj_size(object), the condition evaluates to false, and the
code processes the byte instead of discarding it.</p>
<p>This causes the code to calculate byte_offset = reg + i - cfg-&gt;start_ofs
and writes the byte there, overwriting exactly one byte of the adjacent
instance or object.</p>
<p>Update the boundary check to skip extra bytes correctly by using &gt;=.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-63908"/>
  </entry>
</feed>
