platform/chrome: sensorhub: Bound the EC-reported sensor number
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.4epss 0.2%
exploitation probability
0.2%top 92% of all CVEs
observed exploitation
nono source reports it
In the Linux kernel, the following vulnerability has been resolved:
platform/chrome: sensorhub: Bound the EC-reported sensor number
Each EC FIFO event carries an 8-bit sensor number (in->sensor_num).
cros_ec_sensorhub_ring_handler() validates the FIFO event count, the
per-read count and the ring bound, but not the sensor number, which
cros_ec_sensor_ring_process_event() then uses unchecked to index
sensorhub->batch_state[] - allocated with only sensorhub->sensor_num
entries. A sensor number of sensor_num or larger is an out-of-bounds
read and write of batch_state[].
Validate the sensor number in the ring handler, where each event is read
from the EC, and drop a malformed event before it is used.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/2b602ecf6193ecb9720c78b6728d7e09370b1ff1https://git.kernel.org/stable/c/324880f94ba3c6269a607e04f78a4dd4a66b3f53https://git.kernel.org/stable/c/3a76b87e1d065183e2e7ae5b800cb1f6e84f543dhttps://git.kernel.org/stable/c/3d2636dce0a8fe9eecad29010699847be425dc80https://git.kernel.org/stable/c/4d9bf63ed74f859c6698bc01d8fb216ef9253867https://git.kernel.org/stable/c/5eaf7faa99578ae090030d1e2e6ea3b37a615496https://git.kernel.org/stable/c/833740a2333c2e4db4e02e3d0ffba04e8718a5f3https://git.kernel.org/stable/c/d1b4add68dabfdd6481a4fa198bf3b473d2634d7