CVE-2026-63908 Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem
A boundary check error in the Atmel MXT touch driver allows memory corruption, potentially enabling local attackers to execute code or escalate privileges.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-63908?
CVE-2026-63908 is a memory corruption vulnerability in Linux, published on 19 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
In the Linux kernel, the following vulnerability has been resolved:
Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem
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.
The loop iterates using for (i = 0; i < size; i++). Inside the loop, the condition to skip processing extra bytes is:
if (i > mxt_obj_size(object)) continue;
Since i is a 0-based index, the valid indices for the object are 0 through mxt_obj_size(object) - 1.
When i == mxt_obj_size(object), the condition evaluates to false, and the code processes the byte instead of discarding it.
This causes the code to calculate byte_offset = reg + i - cfg->start_ofs and writes the byte there, overwriting exactly one byte of the adjacent instance or object.
Update the boundary check to skip extra bytes correctly by using >=.
Which versions are affected by CVE-2026-63908?
How do I fix CVE-2026-63908?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-63908 being exploited?
There is no known exploitation of CVE-2026-63908 in the wild and no public exploit code.
Sources
Also known as BELL-CVE-2026-63908, DEBIAN-CVE-2026-63908, GHSA-g59q-3pwp-9gcx, ROOT-OS-UBUNTU-2204-CVE-2026-63908, UBUNTU-CVE-2026-63908.