platform/chrome: sensorhub: Bound the EC-reported sensor number

Overview

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.

Affected

• Linux >= 145d59baff5944b71551ac518d7fd7d377a9c820 < 3a76b87e1d065183e2e7ae5b800cb1f6e84f543d
• Linux >= 145d59baff5944b71551ac518d7fd7d377a9c820 < 2b602ecf6193ecb9720c78b6728d7e09370b1ff1
• Linux >= 145d59baff5944b71551ac518d7fd7d377a9c820 < 324880f94ba3c6269a607e04f78a4dd4a66b3f53
• Linux >= 145d59baff5944b71551ac518d7fd7d377a9c820 < d1b4add68dabfdd6481a4fa198bf3b473d2634d7
• Linux >= 145d59baff5944b71551ac518d7fd7d377a9c820 < 3d2636dce0a8fe9eecad29010699847be425dc80
• Linux >= 145d59baff5944b71551ac518d7fd7d377a9c820 < 5eaf7faa99578ae090030d1e2e6ea3b37a615496
• Linux >= 145d59baff5944b71551ac518d7fd7d377a9c820 < 4d9bf63ed74f859c6698bc01d8fb216ef9253867
• Linux >= 145d59baff5944b71551ac518d7fd7d377a9c820 < 833740a2333c2e4db4e02e3d0ffba04e8718a5f3
• Linux 5.7

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

Vendor advisories

• Red Hat VEX · Moderate · updated 2026-09-14 · vex