In the Linux kernel, the following vulnerability has been resolved: platform/chrome: sensorhub: Fix memory overread in ring handler max_response and… (CVE-2026-93165)
A memory overread vulnerability in the Linux kernel's platform/chrome sensorhub component has been fixed. The flaw arises due to inconsistent reading of max_response and sensor_num values from different EC commands, which can cause a memcpy operation to read beyond the intended buffer. This occurs when a malfunctioning EC firmware causes the input size to be clamped incorrectly, leading to an overread in the sensorhub ring handler.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's platform/chrome sensorhub involves a memory overread in the ring handler function. The max_response value is obtained from cros_ec_get_proto_info(), while sensor_num is obtained from cros_ec_get_sensor_count(). If the EC firmware malfunctions, the input size (msg->insize) may be clamped by cros_ec_cmd_xfer() because it exceeds max_response. This results in fewer bytes being read than expected, causing the subsequent memcpy() in cros_ec_sensorhub_ring_handler() to overread the resp->fifo_info buffer. The fix involves checking the return value of cros_ec_cmd_xfer_status() and aborting if the number of bytes read does not match the expected length.
Potential Impact
This vulnerability can lead to a memory overread, which may cause denial of service or potentially expose sensitive information from kernel memory. The CVSS score of 7.7 (high) reflects the significant confidentiality impact and availability impact, with low attack complexity and no privileges required.
Mitigation Recommendations
A fix is available as the vulnerability has been resolved in the Linux kernel. Users should apply the official kernel updates that include the patch for this issue. No additional mitigation steps are indicated beyond applying the fix.
In the Linux kernel, the following vulnerability has been resolved: platform/chrome: sensorhub: Fix memory overread in ring handler max_response and… (CVE-2026-93165)
Description
A memory overread vulnerability in the Linux kernel's platform/chrome sensorhub component has been fixed. The flaw arises due to inconsistent reading of max_response and sensor_num values from different EC commands, which can cause a memcpy operation to read beyond the intended buffer. This occurs when a malfunctioning EC firmware causes the input size to be clamped incorrectly, leading to an overread in the sensorhub ring handler.
CVSS v3.1
Score 7.7high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's platform/chrome sensorhub involves a memory overread in the ring handler function. The max_response value is obtained from cros_ec_get_proto_info(), while sensor_num is obtained from cros_ec_get_sensor_count(). If the EC firmware malfunctions, the input size (msg->insize) may be clamped by cros_ec_cmd_xfer() because it exceeds max_response. This results in fewer bytes being read than expected, causing the subsequent memcpy() in cros_ec_sensorhub_ring_handler() to overread the resp->fifo_info buffer. The fix involves checking the return value of cros_ec_cmd_xfer_status() and aborting if the number of bytes read does not match the expected length.
Potential Impact
This vulnerability can lead to a memory overread, which may cause denial of service or potentially expose sensitive information from kernel memory. The CVSS score of 7.7 (high) reflects the significant confidentiality impact and availability impact, with low attack complexity and no privileges required.
Mitigation Recommendations
A fix is available as the vulnerability has been resolved in the Linux kernel. Users should apply the official kernel updates that include the patch for this issue. No additional mitigation steps are indicated beyond applying the fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-4wfm-wp45-cw6m
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-93165"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6aade51855bf5e2cf5edc02f
Added to database: 09/19/2026, 01:27:52 UTC
Last enriched: 09/19/2026, 01:43:18 UTC
Last updated: 09/19/2026, 01:43:18 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.