CVE-2026-63908
Received Received - Intake

Boundary Check Bypass in Linux Kernel atmel_mxt_ts Driver

Publication date: 2026-07-19

Last updated on: 2026-07-19

Assigner: kernel.org

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 >=.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-19
Last Modified
2026-07-19
Generated
2026-07-20
AI Q&A
2026-07-19
EPSS Evaluated
N/A
NVD
CVE-2026-63908
EUVD
EUVD-2026-45681

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
atmel atmel_mxt_ts *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a boundary check error in the atmel_mxt_ts driver. When a configuration file provides an object size larger than expected, the driver fails to properly discard extra bytes. The loop condition incorrectly allows processing of one extra byte, which overwrites adjacent memory, potentially corrupting data or causing instability.

Detection Guidance

This vulnerability is specific to the Linux kernel's atmel_mxt_ts driver and requires checking kernel logs or driver behavior for memory corruption issues related to configuration file handling. No direct network detection commands are applicable. Check kernel logs for errors from atmel_mxt_ts with commands like dmesg | grep atmel_mxt_ts or journalctl -k | grep atmel_mxt_ts.

Impact Analysis

This flaw could lead to memory corruption, system crashes, or unintended behavior in devices using the atmel_mxt_ts touchscreen driver. Attackers might exploit it to cause denial-of-service or execute arbitrary code, depending on the system configuration.

Compliance Impact

This vulnerability involves a boundary check flaw in the Linux kernel's atmel_mxt_ts driver, allowing adjacent memory overwrite. While not directly tied to GDPR or HIPAA, such memory corruption could potentially lead to unauthorized data access or system instability, which may impact compliance with data protection standards if exploited.

Mitigation Strategies

Update the Linux kernel to a patched version that includes the fix for CVE-2026-63908. If using a custom or vendor kernel, apply the patch for mxt_prepare_cfg_mem boundary check. Monitor kernel logs for atmel_mxt_ts errors after update.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-63908. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart