Adjacent-object overwrite via off-by-one boundary check
Published Jul 19, 2026 · Updated Jul 19, 2026
Out-of-bounds write in the Linux kernel atmel_mxt_ts driver allows local users to overwrite adjacent memory via a crafted configuration file. The mxt_prepare_cfg_mem loop accepts an index equal to mxt_obj_size(object), calculates byte_offset for the extra byte, and writes into the next instance or object. Reachability requires a configuration file with an oversized object and the affected touchscreen driver; no consequence beyond the one-byte overwrite is documented.
Summary
What happened
Out-of-bounds write in the Linux kernel atmel_mxt_ts driver allows local users to overwrite adjacent memory via a crafted configuration file. The mxt_prepare_cfg_mem loop accepts an index equal to mxt_obj_size(object), calculates byte_offset for the extra byte, and writes into the next instance or object. Reachability requires a configuration file with an oversized object and the affected touchscreen driver; no consequence beyond the one-byte overwrite is documented.
The record
- CVE
- CVE-2026-63908
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.17
- Affected versionversion=50a77c658b80e7e3303e3bcec195b30e2b62d513 <1017e1c6c6c49cccbcda9bbcfa49e50b0b6dad39
- Affected versionversion=50a77c658b80e7e3303e3bcec195b30e2b62d513 <5c3681c3abc35cfac6b702251382312c60d96bc2
- Affected versionversion=50a77c658b80e7e3303e3bcec195b30e2b62d513 <6c6b989b4ebf22b086fdfcac2163b5cb55e34d8f
- Affected versionversion=50a77c658b80e7e3303e3bcec195b30e2b62d513 <7f95f4792c0dc767fcb8e405391e779ab419d55a
- Affected versionversion=50a77c658b80e7e3303e3bcec195b30e2b62d513 <862a1a32b5190241fce7a7d20229539a3926f31e
- Affected versionversion=50a77c658b80e7e3303e3bcec195b30e2b62d513 <ae92e334544263a02d9f99e18385e718c44392c9
- Affected versionversion=50a77c658b80e7e3303e3bcec195b30e2b62d513 <baa0210fb6a9dc3882509a9411b6d284d88fe30e
- Affected versionversion=50a77c658b80e7e3303e3bcec195b30e2b62d513 <e9b62996ba537774f68fecfd7eecb5aec1713952
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo