CVE-2026-81017

Received Received - Intake

Linux Kernel Sensorhub Out-of-Bounds Read

Publication date: 2026-09-11

Last updated on: 2026-09-11

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-11

Last Modified

2026-09-11

Generated

2026-09-12

AI Q&A

2026-09-12

EPSS Evaluated

N/A

NVD

CVE-2026-81017

EUVD

EUVD-2026-76340

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability is in the Linux kernel's platform/chrome sensorhub component. It involves an out-of-bounds read and write issue where the sensor number from an EC FIFO event is not properly validated. The sensor number is used to index an array that is only allocated for a limited number of sensors, leading to potential memory corruption if the sensor number is too large.

Detection Guidance

This vulnerability is specific to the Linux kernel's sensorhub driver and cannot be detected via network commands. Check kernel logs for EC sensorhub errors or crashes using 'dmesg | grep sensorhub' or 'journalctl -k | grep sensorhub'.

Impact Analysis

This vulnerability could allow an attacker to cause memory corruption, potentially leading to system crashes, privilege escalation, or arbitrary code execution. It may also enable unauthorized access to sensitive data or denial-of-service conditions on affected systems.

Mitigation Strategies

Update your Linux kernel to the latest patched version. If using a distribution kernel, apply vendor security updates immediately. Monitor kernel logs for related errors after updating.

Hi! I’m here to help you understand CVE-2026-81017. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70