Linux
HID: intel-thc-hid: intel-quickspi: validate report size before copy
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 9d8d51735a3af40b722346931a6a1e50227df4b5, < 6fcefe71aeb524f6e77fe586fe85d873745e917c
- >= 9d8d51735a3af40b722346931a6a1e50227df4b5, < ee8ad1bb1e96164d51089b1182f1bd5f187e7baa
- >= 9d8d51735a3af40b722346931a6a1e50227df4b5, < a59cf84441f9a17323c89452cec2bf16724c48a9
Fixed in 6fcefe71aeb524f6e77fe586fe85d873745e917c, ee8ad1bb1e96164d51089b1182f1bd5f187e7baa, a59cf84441f9a17323c89452cec2bf16724c48a9
- 6.14
Fixed in 0, 6.18.50, 7.2.4, 7.3
Mitigation
Upgrade Linux to 6fcefe71aeb524f6e77fe586fe85d873745e917c or ee8ad1bb1e96164d51089b1182f1bd5f187e7baa or a59cf84441f9a17323c89452cec2bf16724c48a9 or later.
Upgrade Linux to 0 or 6.18.50 or 7.2.4 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.