CVE-2026-93165

HIGHPre-NVD 7.77.7—
EchelonGraph scoreHIGH confidence

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.7EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.7Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In the Linux kernel, the following vulnerability has been resolved:

platform/chrome: sensorhub: Fix memory overread in ring handler

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.

CVSS v3
7.7
EG Score
7.7HIGHhigh confidence
EG Risk
39
EG Risk 39/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity77% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (8)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

platform/chrome: sensorhub: Fix memory overread in ring handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ee0403520cdbcf87e853df9aaa9b518a0684ed38
generic

platform/chrome: sensorhub: Fix memory overread in ring handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d1ceb2b2324717fa30b44d56ef0c52813e239569
generic

platform/chrome: sensorhub: Fix memory overread in ring handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98604cc8fd2578442f49cd113481e8fc83bc0ad3
generic

platform/chrome: sensorhub: Fix memory overread in ring handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86bcfab7dff6f0a61cbe0660e5176e907353141b
generic

platform/chrome: sensorhub: Fix memory overread in ring handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/847a5ba0ac75f609e3f88da905251f7a76179145
generic

platform/chrome: sensorhub: Fix memory overread in ring handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e901aaf95828364b05a2120a1bea1a1669bdc9a
generic

platform/chrome: sensorhub: Fix memory overread in ring handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7780d93ae28f31fe517417c9451255315d1ad584
generic

platform/chrome: sensorhub: Fix memory overread in ring handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6268f46d83875d294d75b68b97a5b79953744598

Vendor Advisories for CVE-2026-93165(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 26× in last 7d / 70× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 03:31 UTCEG score recompute
  2. 2026-10-05 03:31 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 14:52 UTCGHSA enrichment
  5. 2026-10-04 02:13 UTCEG score recompute
  6. 2026-10-04 02:13 UTCGHSA enrichment
  7. 2026-10-03 13:35 UTCGHSA enrichment
  8. 2026-10-03 00:56 UTCEG score recompute
  9. 2026-10-03 00:56 UTCGHSA enrichment
  10. 2026-10-02 12:17 UTCGHSA enrichment
  11. 2026-10-01 22:52 UTCEG score recompute
  12. 2026-10-01 22:52 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 10:14 UTCGHSA enrichment
  15. 2026-09-30 21:35 UTCEG score recompute
  16. 2026-09-30 21:35 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 08:52 UTCGHSA enrichment
  19. 2026-09-29 20:14 UTCEG score recompute
  20. 2026-09-29 20:13 UTCGHSA enrichment
  21. 2026-09-29 07:32 UTCEG score recompute
  22. 2026-09-29 07:32 UTCGHSA enrichment
  23. 2026-09-28 18:54 UTCEG score recompute
  24. 2026-09-28 18:54 UTCGHSA enrichment
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 45 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 06:15 UTCGHSA enrichment
  3. 2026-09-27 17:37 UTCEG score recompute
  4. 2026-09-27 17:36 UTCGHSA enrichment
  5. 2026-09-27 13:49 UTCEPSS rescore
  6. 2026-09-27 04:57 UTCGHSA enrichment
  7. 2026-09-26 16:17 UTCEG score recompute
  8. 2026-09-26 16:17 UTCGHSA enrichment
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 03:34 UTCEG score recompute
  11. 2026-09-26 03:34 UTCGHSA enrichment
  12. 2026-09-25 14:54 UTCGHSA enrichment
  13. 2026-09-25 02:14 UTCEG score recompute
  14. 2026-09-25 02:14 UTCGHSA enrichment
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-24 13:35 UTCGHSA enrichment
  17. 2026-09-24 00:56 UTCEG score recompute
  18. 2026-09-24 00:56 UTCGHSA enrichment
  19. 2026-09-23 17:54 UTCEPSS rescore
  20. 2026-09-23 12:17 UTCGHSA enrichment
  21. 2026-09-22 23:37 UTCEG score recompute
  22. 2026-09-22 23:37 UTCGHSA enrichment
  23. 2026-09-22 16:01 UTCEPSS rescore
  24. 2026-09-22 10:58 UTCGHSA enrichment
  25. 2026-09-21 22:20 UTCEG score recompute
  26. 2026-09-21 22:19 UTCGHSA enrichment
  27. 2026-09-21 21:09 UTCEPSS rescore
  28. 2026-09-21 09:40 UTCGHSA enrichment
  29. 2026-09-20 21:01 UTCEG score recompute
  30. 2026-09-20 21:01 UTCGHSA enrichment
  31. 2026-09-20 20:16 UTCEPSS rescore
  32. 2026-09-20 08:22 UTCGHSA enrichment
  33. 2026-09-19 19:43 UTCEG score recompute
  34. 2026-09-19 19:43 UTCGHSA enrichment
  35. 2026-09-19 07:04 UTCEG score recompute
  36. 2026-09-19 07:04 UTCGHSA enrichment
  37. 2026-09-18 19:28 UTCEPSS rescore
  38. 2026-09-18 18:26 UTCEG score recompute
  39. 2026-09-18 18:26 UTCGHSA enrichment
  40. 2026-09-18 18:00 UTCEG score recompute▲ 7.70
  41. 2026-09-18 18:00 UTCGHSA enrichment
  42. 2026-09-18 17:59 UTCMITRE cvelistV5CVSS v3 → 7.7 · severity → HIGH
  43. 2026-09-17 17:24 UTCNVD update
  44. 2026-09-17 16:21 UTCEG score recompute
  45. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93165?
CVE-2026-93165 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: platform/chrome: sensorhub: Fix memory overread in ring handler maxresponse and sensornum are read from different EC commands: maxresponse is from crosecgetproto_info(). ecdev->maxresponse = info->maxresponsepacket_size -…
When was CVE-2026-93165 disclosed?
CVE-2026-93165 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93165 actively exploited?
CVE-2026-93165 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93165?
CVE-2026-93165 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93165?
No fix for CVE-2026-93165 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-93165 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-93165

Explore →

Is Your Infrastructure Affected by CVE-2026-93165?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs