Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem
3Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
ssvc Trackepss 0.2%
probabilidade de exploração
0.2%top 89% das CVEs
exploração observada
nãonenhuma fonte reporta
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 >=.
Produtos afetados
Linux · LinuxReferências
https://git.kernel.org/stable/c/1017e1c6c6c49cccbcda9bbcfa49e50b0b6dad39https://git.kernel.org/stable/c/5c3681c3abc35cfac6b702251382312c60d96bc2https://git.kernel.org/stable/c/6c6b989b4ebf22b086fdfcac2163b5cb55e34d8fhttps://git.kernel.org/stable/c/7f95f4792c0dc767fcb8e405391e779ab419d55ahttps://git.kernel.org/stable/c/862a1a32b5190241fce7a7d20229539a3926f31ehttps://git.kernel.org/stable/c/ae92e334544263a02d9f99e18385e718c44392c9https://git.kernel.org/stable/c/baa0210fb6a9dc3882509a9411b6d284d88fe30ehttps://git.kernel.org/stable/c/e9b62996ba537774f68fecfd7eecb5aec1713952