Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 50a77c658b80e7e3303e3bcec195b30e2b62d513 · < 7f95f4792c0dc767fcb8e405391e779ab419d55a| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The atmel_mxt_ts driver has an incorrect boundary check when processing a configuration file with an object size larger than the driver expects. Processing such a file can overwrite one byte of an adjacent instance or object. The input does not specify whether exploitation requires local access, authentication, or user interaction.
Engineers running Linux kernels with the atmel_mxt_ts driver should check their kernel versions; affected versions are not specified.