platform/chrome: sensorhub: Fix memory overread in ring handler
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 145d59baff5944b71551ac518d7fd7d377a9c820 · fixed in 98604cc8fd2578442f49cd113481e8fc83bc0ad3; From 145d59baff5944b71551ac518d7fd7d377a9c820 · fixed in 86bcfab7dff6f0a61cbe0660e5176e907353141b; From 145d59baff5944b71551ac518d7fd7d377a9c820 · fixed in 7e901aaf95828364b05a2120a1bea1a1669bdc9a; From 145d59baff5944b71551ac518d7fd7d377a9c820 · fixed in 7780d93ae28f31fe517417c9451255315d1ad584; From 145d59baff5944b71551ac518d7fd7d377a9c820 · fixed in ee0403520cdbcf87e853df9aaa9b518a0684ed38; From 145d59baff5944b71551ac518d7fd7d377a9c820 · fixed in 847a5ba0ac75f609e3f88da905251f7a76179145; From 145d59baff5944b71551ac518d7fd7d377a9c820 · fixed in 6268f46d83875d294d75b68b97a5b79953744598; From 145d59baff5944b71551ac518d7fd7d377a9c820 · fixed in d1ceb2b2324717fa30b44d56ef0c52813e239569
- Linux Linux
5.7
- KernelLinux
From 5.7.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6
References 8
git.kernel.org
- stable/c/98604cc8fd2578442f49cd113481e8fc83bc0ad3
- stable/c/86bcfab7dff6f0a61cbe0660e5176e907353141b
- stable/c/7e901aaf95828364b05a2120a1bea1a1669bdc9a
- stable/c/7780d93ae28f31fe517417c9451255315d1ad584
- stable/c/ee0403520cdbcf87e853df9aaa9b518a0684ed38
- stable/c/847a5ba0ac75f609e3f88da905251f7a76179145
- stable/c/6268f46d83875d294d75b68b97a5b79953744598
- stable/c/d1ceb2b2324717fa30b44d56ef0c52813e239569