CVE-2026-89620 (GCVE-0-2026-89620)
Vulnerability from cvelistv5
Published
2026-09-11 19:45
Modified
2026-10-19 08:49
Severity ?
7.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: HID: intel-thc-hid: intel-quickspi: validate report size before copy write_cmd_to_txdma() builds an output report in qsdev->report_buf, a heap buffer allocated in quickspi_alloc_report_buf() to the device-descriptor derived max_report_len (a few hundred bytes for a touch controller). It copies the caller-supplied report into that buffer: memcpy(write_buf->content, report_buf, report_buf_len); The HID core caps a report at HID_MAX_BUFFER_SIZE (16384) by default, and quickspi_hid_ll_driver does not set max_buffer_size, so the length reaches the driver unbounded. A hidraw SET_REPORT/SET_FEATURE ioctl carrying a report larger than max_report_len therefore overflows report_buf with attacker-controlled length and content. Record the report_buf allocation size and reject reports that do not fit before copying, matching the equivalent guard in the intel-quicki2c sibling (quicki2c_init_write_buf()) and the hid-goodix-spi fix. write_cmd_to_txdma() writes the output report header ahead of the content in the same buffer, so size the allocation to cover the header as well. That keeps the added bound from rejecting a maximum-sized report.
References
Impacted products
Vendor Product Version
Linux Linux Version: 9d8d51735a3af40b722346931a6a1e50227df4b5
Version: 9d8d51735a3af40b722346931a6a1e50227df4b5
Version: 9d8d51735a3af40b722346931a6a1e50227df4b5
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/hid/intel-thc-hid/intel-quickspi/pci-quickspi.c",
            "drivers/hid/intel-thc-hid/intel-quickspi/quickspi-dev.h",
            "drivers/hid/intel-thc-hid/intel-quickspi/quickspi-protocol.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "6fcefe71aeb524f6e77fe586fe85d873745e917c",
              "status": "affected",
              "version": "9d8d51735a3af40b722346931a6a1e50227df4b5",
              "versionType": "git"
            },
            {
              "lessThan": "ee8ad1bb1e96164d51089b1182f1bd5f187e7baa",
              "status": "affected",
              "version": "9d8d51735a3af40b722346931a6a1e50227df4b5",
              "versionType": "git"
            },
            {
              "lessThan": "a59cf84441f9a17323c89452cec2bf16724c48a9",
              "status": "affected",
              "version": "9d8d51735a3af40b722346931a6a1e50227df4b5",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/hid/intel-thc-hid/intel-quickspi/pci-quickspi.c",
            "drivers/hid/intel-thc-hid/intel-quickspi/quickspi-dev.h",
            "drivers/hid/intel-thc-hid/intel-quickspi/quickspi-protocol.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.14"
            },
            {
              "lessThan": "6.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.50",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.50",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.4",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nHID: intel-thc-hid: intel-quickspi: validate report size before copy\n\nwrite_cmd_to_txdma() builds an output report in qsdev-\u003ereport_buf, a heap\nbuffer allocated in quickspi_alloc_report_buf() to the device-descriptor\nderived max_report_len (a few hundred bytes for a touch controller).  It\ncopies the caller-supplied report into that buffer:\n\n    memcpy(write_buf-\u003econtent, report_buf, report_buf_len);\n\nThe HID core caps a report at HID_MAX_BUFFER_SIZE (16384) by default, and\nquickspi_hid_ll_driver does not set max_buffer_size, so the length reaches\nthe driver unbounded.  A hidraw SET_REPORT/SET_FEATURE ioctl carrying a\nreport larger than max_report_len therefore overflows report_buf with\nattacker-controlled length and content.\n\nRecord the report_buf allocation size and reject reports that do not fit\nbefore copying, matching the equivalent guard in the intel-quicki2c\nsibling (quicki2c_init_write_buf()) and the hid-goodix-spi fix.\n\nwrite_cmd_to_txdma() writes the output report header ahead of the content\nin the same buffer, so size the allocation to cover the header as well.\nThat keeps the added bound from rejecting a maximum-sized report."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - An unprivileged local process reaches write_cmd_to_txdma() via hidraw write() or HIDIOCSOUTPUT/HIDIOCSFEATURE ioctls on the Intel THC HIDSPI touch controller\u0027s /dev/hidraw node; this is an onboard PCI device, not a network or USB-plug path.\nAC:L - A single SET_REPORT/SET_FEATURE with a length between the device-descriptor max_report_len (typically a few hundred bytes) and HID_MAX_BUFFER_SIZE (16384) deterministically overflows report_buf with attacker-chosen bytes; no race or uninfluenced condition is required.\nPR:L - hidraw_open() performs no capability or namespace checks, and systemd uaccess grants the seated user access to /dev/hidraw*, so a normal unprivileged local account can trigger the overflow.\nUI:N - The attacker opens the hidraw node and issues the ioctl or write themselves; no separate victim action is required.\nS:U - The overflow corrupts kernel heap in the host HID/THC driver and any resulting privilege escalation stays within the same kernel security authority.\nC:H - The memcpy writes attacker-controlled data past a small heap buffer (up to ~16KB), which can corrupt adjacent objects and be turned into an arbitrary kernel read primitive.\nI:H - The same attacker-controlled heap overflow can overwrite neighboring heap metadata and objects, enabling an arbitrary write and kernel control-flow hijack.\nA:H - Out-of-bounds heap writes of this size reliably cause kernel oops, panic, or SLUB corruption, and the request can be repeated at will."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T08:49:52.704Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/6fcefe71aeb524f6e77fe586fe85d873745e917c"
        },
        {
          "url": "https://git.kernel.org/stable/c/ee8ad1bb1e96164d51089b1182f1bd5f187e7baa"
        },
        {
          "url": "https://git.kernel.org/stable/c/a59cf84441f9a17323c89452cec2bf16724c48a9"
        }
      ],
      "title": "HID: intel-thc-hid: intel-quickspi: validate report size before copy",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-89620",
    "datePublished": "2026-09-11T19:45:18.758Z",
    "dateReserved": "2026-09-11T19:38:34.736Z",
    "dateUpdated": "2026-10-19T08:49:52.704Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.