GHSA-G59Q-3PWP-9GCX

Vulnerability from github – Published: 2026-07-19 18:31 – Updated: 2026-07-19 18:31
VLAI
Details

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

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-63908"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-19T16:17:08Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nInput: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem\n\nWhen a configuration file provides an object size that is larger than the\ndriver\u0027s known mxt_obj_size(object), the driver intends to discard the\nextra bytes.\n\nThe loop iterates using for (i = 0; i \u003c size; i++). Inside the loop, the\ncondition to skip processing extra bytes is:\n\n    if (i \u003e mxt_obj_size(object))\n        continue;\n\nSince i is a 0-based index, the valid indices for the object are 0 through\nmxt_obj_size(object) - 1.\n\nWhen i == mxt_obj_size(object), the condition evaluates to false, and the\ncode processes the byte instead of discarding it.\n\nThis causes the code to calculate byte_offset = reg + i - cfg-\u003estart_ofs\nand writes the byte there, overwriting exactly one byte of the adjacent\ninstance or object.\n\nUpdate the boundary check to skip extra bytes correctly by using \u003e=.",
  "id": "GHSA-g59q-3pwp-9gcx",
  "modified": "2026-07-19T18:31:45Z",
  "published": "2026-07-19T18:31:45Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-63908"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1017e1c6c6c49cccbcda9bbcfa49e50b0b6dad39"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/5c3681c3abc35cfac6b702251382312c60d96bc2"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/6c6b989b4ebf22b086fdfcac2163b5cb55e34d8f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7f95f4792c0dc767fcb8e405391e779ab419d55a"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/862a1a32b5190241fce7a7d20229539a3926f31e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ae92e334544263a02d9f99e18385e718c44392c9"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/baa0210fb6a9dc3882509a9411b6d284d88fe30e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e9b62996ba537774f68fecfd7eecb5aec1713952"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.