Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Timeline

  1. ID reserved

    By Linux

  2. Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63908, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (21 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 50a77c658b80e7e3303e3bcec195b30e2b62d513 – < 862a1a32b5190241fce7a7d20229539a3926f31e
    • affected 50a77c658b80e7e3303e3bcec195b30e2b62d513 – < 5c3681c3abc35cfac6b702251382312c60d96bc2
    • affected 50a77c658b80e7e3303e3bcec195b30e2b62d513 – < 1017e1c6c6c49cccbcda9bbcfa49e50b0b6dad39
    • affected 50a77c658b80e7e3303e3bcec195b30e2b62d513 – < e9b62996ba537774f68fecfd7eecb5aec1713952
    • affected 50a77c658b80e7e3303e3bcec195b30e2b62d513 – < ae92e334544263a02d9f99e18385e718c44392c9
    • affected 50a77c658b80e7e3303e3bcec195b30e2b62d513 – < 7f95f4792c0dc767fcb8e405391e779ab419d55a
    • affected 50a77c658b80e7e3303e3bcec195b30e2b62d513 – < 6c6b989b4ebf22b086fdfcac2163b5cb55e34d8f
    • affected 50a77c658b80e7e3303e3bcec195b30e2b62d513 – < baa0210fb6a9dc3882509a9411b6d284d88fe30e
  • Linux · Linux

    • affected 3.17
    • unaffected < 3.17
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.93 – ≤ 6.12.*
    • unaffected 6.18.35 – ≤ 6.18.*
    • unaffected 7.0.12 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63908 badge
[![CVE-2026-63908](https://cveledger.app/badge/CVE-2026-63908.svg)](https://cveledger.app/cve/CVE-2026-63908)

Record last updated .