PatchSiren cyber security CVE debrief
CVE-2026-93165 Linux CVE debrief
A memory overread vulnerability was found in the Linux kernel's platform/chrome sensorhub. The issue arises from `max_response` and `sensor_num` being read from different EC commands, potentially causing the `msg->insize` to be clamped in `cros_ec_cmd_xfer()`. This could result in the subsequent `memcpy()` in `cros_ec_sensorhub_ring_handler()` overreading the `resp->fifo_info` buffer.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 7.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-17
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-17
- Advisory updated
- 2026-09-18
Who should care
Defenders responsible for maintaining the Linux kernel and EC firmware should be aware of this vulnerability and take necessary actions to prevent potential memory overread issues.
Why it matters
A memory overread vulnerability in the Linux kernel's platform/chrome sensorhub requires defenders to verify EC firmware integrity, ensure Linux kernel updates, and monitor system logs to prevent potential issues.
- Verify EC firmware integrity to prevent potential memory overread issues
- Ensure Linux kernel updates to prevent exploitation
- Monitor system logs for potential memory overread issues
- Assess exposure of Linux kernel and EC firmware configurations
Technical summary
The vulnerability arises from `max_response` and `sensor_num` being read from different EC commands, potentially causing the `msg->insize` to be clamped in `cros_ec_cmd_xfer()`. This could result in the subsequent `memcpy()` in `cros_ec_sensorhub_ring_handler()` overreading the `resp->fifo_info` buffer. The issue affects the Linux kernel's platform/chrome sensorhub, and defenders should prioritize verifying the integrity of the EC firmware and ensuring that the Linux kernel is updated with the necessary patches to prevent potential memory overread issues.
Defensive priority
Defenders should prioritize verifying the integrity of the EC firmware and ensuring that the Linux kernel is updated with the necessary patches to prevent potential memory overread issues.
Recommended defensive actions
- Verify the integrity of the EC firmware
- Ensure that the Linux kernel is updated with the necessary patches
- Monitor system logs for potential memory overread issues
- Assess exposure of Linux kernel and EC firmware configurations
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The vulnerability was resolved by checking the return value of `cros_ec_cmd_xfer_status()` and aborting if the number of bytes read does not match the expected length. This fix ensures that the memcpy() in cros_ec_sensorhub_ring_handler() does not overread the resp->fifo_info buffer. Defenders should verify EC firmware integrity, ensure Linux kernel updates, and monitor system logs to prevent potential issues.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-93165 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-93165
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-93165 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-93165
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/6268f46d83875d294d75b68b97a5b79953744598
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/7780d93ae28f31fe517417c9451255315d1ad584
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/7e901aaf95828364b05a2120a1bea1a1669bdc9a
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/847a5ba0ac75f609e3f88da905251f7a76179145
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/86bcfab7dff6f0a61cbe0660e5176e907353141b
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/98604cc8fd2578442f49cd113481e8fc83bc0ad3
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/d1ceb2b2324717fa30b44d56ef0c52813e239569
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/ee0403520cdbcf87e853df9aaa9b518a0684ed38
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.