In the Linux kernel, the following vulnerability has been resolved: Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem When a… (CVE-2026-63908)
A boundary check vulnerability in the Linux kernel's atmel_mxt_ts driver was fixed. The driver incorrectly allowed processing of one byte beyond the intended object size, causing an overwrite of an adjacent object byte. This was due to an off-by-one error in the loop condition checking the object size. The fix updates the boundary check to correctly skip extra bytes by using a greater-than-or-equal comparison.
AI Analysis
Technical Summary
The Linux kernel atmel_mxt_ts driver had a boundary check flaw in the mxt_prepare_cfg_mem function. When a configuration file specified an object size larger than the driver's known size, the loop iterated over the bytes but failed to properly skip the byte at the index equal to the object size. This off-by-one error caused a single byte overwrite in adjacent memory by calculating an incorrect byte offset and writing data there. The vulnerability was resolved by changing the boundary check condition from 'i > mxt_obj_size(object)' to 'i >= mxt_obj_size(object)', preventing the out-of-bounds write.
Potential Impact
The vulnerability allows a single byte overwrite of adjacent memory within the kernel driver context. This could potentially lead to memory corruption, which might affect kernel stability or security depending on the overwritten data. No known exploits are reported in the wild. The impact is limited to the atmel_mxt_ts driver handling of configuration data.
Mitigation Recommendations
A fix is available and has been applied to the Linux kernel source code to correct the boundary check condition. Users and administrators should update to the fixed Linux kernel version containing this patch. Since this is a kernel-level vulnerability, applying the official kernel update is the recommended remediation.
In the Linux kernel, the following vulnerability has been resolved: Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem When a… (CVE-2026-63908)
Description
A boundary check vulnerability in the Linux kernel's atmel_mxt_ts driver was fixed. The driver incorrectly allowed processing of one byte beyond the intended object size, causing an overwrite of an adjacent object byte. This was due to an off-by-one error in the loop condition checking the object size. The fix updates the boundary check to correctly skip extra bytes by using a greater-than-or-equal comparison.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel atmel_mxt_ts driver had a boundary check flaw in the mxt_prepare_cfg_mem function. When a configuration file specified an object size larger than the driver's known size, the loop iterated over the bytes but failed to properly skip the byte at the index equal to the object size. This off-by-one error caused a single byte overwrite in adjacent memory by calculating an incorrect byte offset and writing data there. The vulnerability was resolved by changing the boundary check condition from 'i > mxt_obj_size(object)' to 'i >= mxt_obj_size(object)', preventing the out-of-bounds write.
Potential Impact
The vulnerability allows a single byte overwrite of adjacent memory within the kernel driver context. This could potentially lead to memory corruption, which might affect kernel stability or security depending on the overwritten data. No known exploits are reported in the wild. The impact is limited to the atmel_mxt_ts driver handling of configuration data.
Mitigation Recommendations
A fix is available and has been applied to the Linux kernel source code to correct the boundary check condition. Users and administrators should update to the fixed Linux kernel version containing this patch. Since this is a kernel-level vulnerability, applying the official kernel update is the recommended remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-g59q-3pwp-9gcx
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63908"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27ab2a4a8d598912f5c5
Added to database: 07/19/2026, 19:38:19 UTC
Last enriched: 07/19/2026, 20:09:16 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.