CVE-2026-63908 — Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem
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 >=.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 50a77c658b80e7e3303e3bcec195b30e2b62d513 and < 862a1a32b5190241fce7a7d20229539a3926f31e≥ 50a77c658b80e7e3303e3bcec195b30e2b62d513 and < 5c3681c3abc35cfac6b702251382312c60d96bc2≥ 50a77c658b80e7e3303e3bcec195b30e2b62d513 and < 1017e1c6c6c49cccbcda9bbcfa49e50b0b6dad39≥ 50a77c658b80e7e3303e3bcec195b30e2b62d513 and < e9b62996ba537774f68fecfd7eecb5aec1713952≥ 50a77c658b80e7e3303e3bcec195b30e2b62d513 and < ae92e334544263a02d9f99e18385e718c44392c9≥ 50a77c658b80e7e3303e3bcec195b30e2b62d513 and < 7f95f4792c0dc767fcb8e405391e779ab419d55a≥ 50a77c658b80e7e3303e3bcec195b30e2b62d513 and < 6c6b989b4ebf22b086fdfcac2163b5cb55e34d8f≥ 50a77c658b80e7e3303e3bcec195b30e2b62d513 and < baa0210fb6a9dc3882509a9411b6d284d88fe30e and 1 moreversion 3.17 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Awaiting Analysis
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/6c6b989b4ebf22b086fdfcac2163b5cb55e34d8f
- git.kernel.org/stable/c/862a1a32b5190241fce7a7d20229539a3926f31e
- git.kernel.org/stable/c/7f95f4792c0dc767fcb8e405391e779ab419d55a
- git.kernel.org/stable/c/baa0210fb6a9dc3882509a9411b6d284d88fe30e
- git.kernel.org/stable/c/e9b62996ba537774f68fecfd7eecb5aec1713952
- git.kernel.org/stable/c/ae92e334544263a02d9f99e18385e718c44392c9
- git.kernel.org/stable/c/1017e1c6c6c49cccbcda9bbcfa49e50b0b6dad39
- git.kernel.org/stable/c/5c3681c3abc35cfac6b702251382312c60d96bc2
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 15h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 15h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-63908 is "Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.