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 >=.
Published: 2026-07-19
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The atmel_mxt_ts driver performs a boundary check on configuration file data but incorrectly allows the last byte of an object to be processed, resulting in a one‑byte write into adjacent kernel memory. This unchecked write can corrupt kernel data structures or control information, providing a potential local privilege escalation or system instability, as the flaw is a classic out‑of‑bounds write classified as CWE‑787.

Affected Systems

The flaw affects Linux kernels that include the atmel_mxt_ts driver prior to the patch. All distributions shipping that kernel revision are impacted; however, the database does not specify exact version numbers. Administrators should inspect the atmel_mxt_ts driver version in their kernel source and apply the recent patch that implements the correct >= check.

Risk and Exploitability

The EPSS score is reported as less than 1% and the vulnerability is not in the CISA KEV catalog, indicating a low likelihood of exploitation in the wild. Based on the description, it is inferred that the attack vector involves a local user who can supply a malicious configuration file to the driver, potentially allowing that user to corrupt kernel memory. While no active exploits are documented, the potential impact on system integrity and stability makes timely remediation prudent.

Generated by OpenCVE AI on August 3, 2026 at 02:15 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the kernel patch that implements the >= comparison.
  • If an upgrade cannot be performed immediately, disable the atmel_mxt_ts driver or block loading of external touchscreen configuration files.
  • Monitor system logs for abnormal kernel memory corruption or crash events.

Generated by OpenCVE AI on August 3, 2026 at 02:15 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
History

Mon, 27 Jul 2026 20:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-120

Wed, 22 Jul 2026 19:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-120

Wed, 22 Jul 2026 00:15:00 +0000


Sun, 19 Jul 2026 15:30:00 +0000

Type Values Removed Values 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 >=.
Title Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-07-19T14:55:14.349Z

Reserved: 2026-07-19T07:54:57.020Z

Link: CVE-2026-63908

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity :

Publid Date: 2026-07-19T00:00:00Z

Links: CVE-2026-63908 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-03T02:30:07Z

Weaknesses