CVE-2026-63908

UnknownEPSS 0.21%

Last modified

CVE-2026-63908 is a vulnerability of currently unknown severity. 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 >=.. EPSS estimates a 0.21% chance of exploitation in the next 30 days.

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

Metrics

EPSS Probability
0.21%

11.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 50a77c658b80e7e3303e3bcec195b30e2b62d513, < 862a1a32b5190241fce7a7d20229539a3926f31e; >= 50a77c658b80e7e3303e3bcec195b30e2b62d513, < 5c3681c3abc35cfac6b702251382312c60d96bc2; >= 50a77c658b80e7e3303e3bcec195b30e2b62d513, < 1017e1c6c6c49cccbcda9bbcfa49e50b0b6dad39; >= 50a77c658b80e7e3303e3bcec195b30e2b62d513, < e9b62996ba537774f68fecfd7eecb5aec1713952; >= 50a77c658b80e7e3303e3bcec195b30e2b62d513, < ae92e334544263a02d9f99e18385e718c44392c9; >= 50a77c658b80e7e3303e3bcec195b30e2b62d513, < 7f95f4792c0dc767fcb8e405391e779ab419d55a; >= 50a77c658b80e7e3303e3bcec195b30e2b62d513, < 6c6b989b4ebf22b086fdfcac2163b5cb55e34d8f; >= 50a77c658b80e7e3303e3bcec195b30e2b62d513, < baa0210fb6a9dc3882509a9411b6d284d88fe30e
LinuxLinux3.17

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-63908?
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 >=.
How severe is CVE-2026-63908?
Severity scoring for CVE-2026-63908 is pending analysis. The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2026-63908?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-63908?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST