CVE-2026-93165

platform/chrome: sensorhub: Fix memory overread in ring handler

HIGH
7.7
CVSS Score
Published: September 17, 2026 at 04:11 PM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.7
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: platform/chrome: sensorhub: Fix memory overread in ring handler `max_response` and `sensor_num` are read from different EC commands: - `max_response` is from cros_ec_get_proto_info(). ec_dev->max_response = info->max_response_packet_size - sizeof(struct ec_host_response); - `sensor_num` is from cros_ec_get_sensor_count(). sensor_num = cros_ec_get_sensor_count(ec); With a malfunctioning EC firmware, it is possible that the `msg->insize` (i.e., `fifo_info_length` in the context) could be clamped in cros_ec_cmd_xfer() because `msg->insize` is greater than `max_response`. int fifo_info_length = sizeof(struct ec_response_motion_sense_fifo_info) + sizeof(u16) * sensorhub->sensor_num; This means the number of read bytes could be less than expected. As a result, the subsequent memcpy() in cros_ec_sensorhub_ring_handler() overreads the `resp->fifo_info` buffer. Check the return value of cros_ec_cmd_xfer_status() and abort if the number of bytes read does not match the expected length.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

145d59baff5944b71551ac518d7fd7d377a9c8205.7
Vendor states this is fixed in 6268f46d83875d294d75b68b97a5b79953744598 (fixed)
Vendor states this is fixed in 7780d93ae28f31fe517417c9451255315d1ad584 (fixed)
Vendor states this is fixed in 7e901aaf95828364b05a2120a1bea1a1669bdc9a (fixed)
Vendor states this is fixed in 847a5ba0ac75f609e3f88da905251f7a76179145 (fixed)
Vendor states this is fixed in 86bcfab7dff6f0a61cbe0660e5176e907353141b (fixed)
Vendor states this is fixed in 98604cc8fd2578442f49cd113481e8fc83bc0ad3 (fixed)
Vendor states this is fixed in d1ceb2b2324717fa30b44d56ef0c52813e239569 (fixed)
Vendor states this is fixed in ee0403520cdbcf87e853df9aaa9b518a0684ed38 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.7 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.7HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card