Look up another CVE · open CVE-2026-93165 in the interactive tracker
CVE-2026-93165
platform/chrome: sensorhub: Fix memory overread in ring handler
Published 2026-09-17 (31 days ago) by the Linux kernel CNA. Subsystem drivers/platform. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-93165 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixedDLA-4841-1 · 2026-10-17 · text | 6.1.190-1 | Update the kernel and reboot. DLA-4841-1 shipped the fix on 2026-10-17, in 6.1.190-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
`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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/platform/chrome/cros_ec_sensorhub_ring.c
- What this is
- CHROME HARDWARE PLATFORM SUPPORTMAINTAINERS section matched on drivers/platform/chrome/ · chrome-platform@lists.linux.dev · Maintained
- Kernel module
- cros_ec_sensorhub
Check it on the machine
grep -wE 'CONFIG_CHROME_PLATFORMS|CONFIG_CROS_EC_SENSORHUB' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w cros_ec_sensorhubPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le
- trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- bookworm · linux-6.12Mnot built on amd64/cloud-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k
- M
- a module where it is built at all; some flavours do not build it
- Build switches
- CONFIG_CHROME_PLATFORMS, CONFIG_CROS_EC_SENSORHUB
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-17 (31 days ago)source
- CVSS
- 7.7 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.18%, higher than 7.1% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/platform
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.7 | 5.10.270 | 98604cc8fd25 |
| 5.7 | 5.15.221 | 86bcfab7dff6 |
| 5.7 | 6.1.188 | 7e901aaf9582 |
| 5.7 | 6.6.157 | 7780d93ae28f |
| 5.7 | 6.12.110 | ee0403520cdb |
| 5.7 | 6.18.52 | 847a5ba0ac75 |
| 5.7 | 7.2.6 | 6268f46d8387 |
| 5.7 | 7.3 | d1ceb2b23247 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4841-1 | 2026-10-17 | bookworm 6.1.190-1 | tracker |
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The MOTIONSENSE_CMD_FIFO_INFO bytes that cros_ec_sensorhub_ring_handler() memcpy()s, plus the mismatched max_response (cros_ec_get_proto_info) and sensor_num (MOTIONSENSE_CMD_DUMP via cros_ec_get_sensor_count), arrive from the on-board Chrome EC through cros_ec_irq_thread → event_notifier → cros_ec_sensorhub_event, not from a network protocol or pluggable USB device.
- AC:LAttack complexity, low
- A compromised EC sets dump.sensor_count and GET_PROTOCOL_INFO max_response_packet_size so fifo_info_length exceeds max_response, then sends EC_MKBP_EVENT_SENSOR_FIFO with total_lost != 0. cros_ec_cmd_xfer() clamps insize and the memcpy of fifo_info_length then runs deterministically with no race.
- PR:NPrivileges required, none
- cros_ec_sensorhub_ring_handler() runs from the MKBP IRQ notifier with no capable() or credential check. cros_ec_sensorhub_ring_add() calls cros_ec_sensorhub_ring_fifo_enable(true) at probe, so compromised EC firmware can trigger the FIFO_INFO overread without a host account.
- UI:NUser interaction, none
- FIFO interrupts are armed in cros_ec_sensorhub_ring_add() during driver probe; the EC_MKBP_EVENT_SENSOR_FIFO IRQ alone reaches the memcpy. No victim must open an IIO device, the cros_ec chardev, or take any other action.
- S:UScope, unchanged
- The overread is of the host kernel heap object allocated for sensorhub->msg in cros_ec_sensorhub_probe(); impact stays in the same kernel that runs the sensorhub driver, not a VM, IOMMU, or sandbox boundary.
- C:HConfidentiality impact, high
- After clamping, memcpy(fifo_info, &resp->fifo_info, fifo_info_length) reads past the max_response-sized msg->data allocation into adjacent slab. With dump.sensor_count up to 255 that is hundreds of bytes of kernel heap, and fifo_info->lost[] is later printed in the "Sensor %d: lost: %d" warning, not a few-byte leak.
- I:NIntegrity impact, none
- fifo_info is allocated fifo_info_length bytes in cros_ec_sensorhub_ring_allocate(), so the memcpy destination is in-bounds. fifo_info->count/size are then checked against fifo_size before MOTIONSENSE_CMD_FIFO_READ; this is an overread only, with no OOB write or control-flow hijack.
- A:HAvailability impact, high
- memcpy() of fifo_info_length past the probe kmalloc (sizeof(cros_ec_command)+max_response) can walk off the slab into unmapped or poisoned memory and oops. A malicious EC can report a tiny max_response and large sensor_count to make that overread hundreds of bytes from a small object.