platform/chrome: sensorhub: Fix memory overread in ring handler
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 145d59baff5944b71551ac518d7fd7d377a9c820 · < 847a5ba0ac75f609e3f88da905251f7a76179145| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s ChromeOS sensorhub ring handler can read beyond a response buffer when malfunctioning EC firmware causes a response to be shorter than expected. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the ChromeOS sensorhub driver should check their deployments; affected versions are not specified.