CVE-2025-68777: Input: ti_am335x_tsc - fix off-by-one error in wire_order validation
In the Linux kernel, the following vulnerability has been resolved:
Input: ti_am335x_tsc - fix off-by-one error in wire_order validation
The current validation 'wire_order[i] > ARRAY_SIZE(config_pins)' allows
wire_order[i] to equal ARRAY_SIZE(config_pins), which causes out-of-bounds
access when used as index in 'config_pins[wire_order[i]]'.
Since config_pins has 4 elements (indices 0-3), the valid range for
wire_order should be 0-3. Fix the off-by-one error by using >= instead
of > in the validation check.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects validation in the TI AM335x touchscreen input driver. A bad wire_order value can pass validation and cause an out-of-bounds array access. The available sources do not provide CVSS, impact severity, or evidence of active exploitation, so urgency depends on whether affected embedded Linux systems use this driver.
Executive priority
Do not treat this as an internet-wide emergency based on current evidence. Prioritize validation in embedded Linux and appliance fleets, especially TI AM335x-based devices, then patch through normal kernel or firmware maintenance once vendor-fixed builds are available.
Technical view
The ti_am335x_tsc driver allowed wire_order[i] to equal ARRAY_SIZE(config_pins). Because config_pins has four valid indexes, 0 through 3, that value can be used as an invalid index. The kernel fix changes the check from greater-than to greater-than-or-equal validation across stable branches.
Likely exposure
Most likely exposure is Linux-based embedded or hardware-specific systems using the TI AM335x touchscreen controller driver. General-purpose servers and desktops are less likely to be exposed unless this driver is present and reachable through their kernel configuration or device firmware.
Exploitation context
The provided bundle does not show CISA KEV listing, public exploitation, exploit maturity, or a CVSS score. Treat this as a memory-safety kernel bug with unclear practical exploitability until vendor advisories or downstream distribution guidance provide more detail.
Researcher notes
The core issue is an off-by-one bounds check in wire_order validation before indexing config_pins. Sources identify fixed stable commits but do not state attacker prerequisites, reachable configuration paths, crash behavior, privilege impact, or exploitability. Further assessment should focus on driver inclusion and downstream patch status.
Mitigation direction
Update to a kernel or vendor firmware containing the stable ti_am335x_tsc fix.
Track Linux distribution advisories for backported packages covering CVE-2025-68777.
Prioritize embedded products that include TI AM335x touchscreen hardware or this driver.
Request vendor confirmation for appliances where kernel configuration is not visible.
Validation and detection
Inventory Linux kernel versions across affected embedded and appliance fleets.
Confirm whether the ti_am335x_tsc driver is built, loaded, or included in firmware.
Verify the source or package includes the >= wire_order validation fix.
Map findings to the listed stable kernel commits or downstream vendor advisories.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-68777 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
8Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jan 13, 2026, 15:28 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.