# CVE-2026-63908: Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem

> A boundary check error in the Atmel MXT touch driver allows memory corruption, potentially enabling local attackers to execute code or escalate privileges.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2026
- **Updated:** 19 Jul 2026
- **Also known as:** BELL-CVE-2026-63908, DEBIAN-CVE-2026-63908, GHSA-g59q-3pwp-9gcx, ROOT-OS-UBUNTU-2204-CVE-2026-63908, UBUNTU-CVE-2026-63908

## What is CVE-2026-63908?

CVE-2026-63908 is a memory corruption vulnerability in Linux, published on 19 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-63908?


## How do I fix CVE-2026-63908?

Apply the vendor's patch.

## Is CVE-2026-63908 being exploited?

There is no known exploitation of CVE-2026-63908 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63908 and fix it if it is affected.

What it is: CVE-2026-63908 is a memory corruption vulnerability in Linux, published on 19 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63908 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63908/ (Markdown: https://insights.sbomify.com/CVE-2026-63908/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63908
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63908
- OSV: https://osv.dev/vulnerability/CVE-2026-63908

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63908/
Summaries are generated and may contain mistakes; the official description above is the record.