CVE-2026-63908
Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem
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 >=.
INFO
Published Date :
July 19, 2026, 4:17 p.m.
Last Modified :
July 27, 2026, 5:44 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Solution
- Apply the patch to the atmel_mxt_ts driver.
- Update the Linux kernel to include the fix.
- Verify the boundary check logic.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-63908.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-63908 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-63908
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-63908 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-63908 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 19, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '50a77c658b80e7e3303e3bcec195b30e2b62d513', 'lessThan': '862a1a32b5190241fce7a7d20229539a3926f31e', 'versionType': 'git'}, {'status': 'affected', 'version': '50a77c658b80e7e3303e3bcec195b30e2b62d513', 'lessThan': '5c3681c3abc35cfac6b702251382312c60d96bc2', 'versionType': 'git'}, {'status': 'affected', 'version': '50a77c658b80e7e3303e3bcec195b30e2b62d513', 'lessThan': '1017e1c6c6c49cccbcda9bbcfa49e50b0b6dad39', 'versionType': 'git'}, {'status': 'affected', 'version': '50a77c658b80e7e3303e3bcec195b30e2b62d513', 'lessThan': 'e9b62996ba537774f68fecfd7eecb5aec1713952', 'versionType': 'git'}, {'status': 'affected', 'version': '50a77c658b80e7e3303e3bcec195b30e2b62d513', 'lessThan': 'ae92e334544263a02d9f99e18385e718c44392c9', 'versionType': 'git'}, {'status': 'affected', 'version': '50a77c658b80e7e3303e3bcec195b30e2b62d513', 'lessThan': '7f95f4792c0dc767fcb8e405391e779ab419d55a', 'versionType': 'git'}, {'status': 'affected', 'version': '50a77c658b80e7e3303e3bcec195b30e2b62d513', 'lessThan': '6c6b989b4ebf22b086fdfcac2163b5cb55e34d8f', 'versionType': 'git'}, {'status': 'affected', 'version': '50a77c658b80e7e3303e3bcec195b30e2b62d513', 'lessThan': 'baa0210fb6a9dc3882509a9411b6d284d88fe30e', 'versionType': 'git'}], 'programFiles': ['drivers/input/touchscreen/atmel_mxt_ts.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '3.17'}, {'status': 'unaffected', 'version': '0', 'lessThan': '3.17', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.259', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.210', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.176', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.143', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.93', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.35', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.12', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/input/touchscreen/atmel_mxt_ts.c'], 'defaultStatus': 'affected'}] Added 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 >=. Added Reference https://git.kernel.org/stable/c/1017e1c6c6c49cccbcda9bbcfa49e50b0b6dad39 Added Reference https://git.kernel.org/stable/c/5c3681c3abc35cfac6b702251382312c60d96bc2 Added Reference https://git.kernel.org/stable/c/6c6b989b4ebf22b086fdfcac2163b5cb55e34d8f Added Reference https://git.kernel.org/stable/c/7f95f4792c0dc767fcb8e405391e779ab419d55a Added Reference https://git.kernel.org/stable/c/862a1a32b5190241fce7a7d20229539a3926f31e Added Reference https://git.kernel.org/stable/c/ae92e334544263a02d9f99e18385e718c44392c9 Added Reference https://git.kernel.org/stable/c/baa0210fb6a9dc3882509a9411b6d284d88fe30e Added Reference https://git.kernel.org/stable/c/e9b62996ba537774f68fecfd7eecb5aec1713952