Categories
CVE-2026-93165 high CVSS 7.7

Vulnerability in Linux kernel (CVE-2026-93165)

Summary

Vulnerability in Linux kernel (CVE-2026-93165). Confidential information can be exposed externally. Exploitable via max_response.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-93165 has been found in Linux kernel.
Attackers can target a specific entry point like max_response over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2026-93165" on the vendor's site.

CVE-2026-93165 (Linux kernel) — CVSS v3 7.7
Attack vector: local / unauthenticated / no user interaction
Attack surface: max_response / sensor_num / fifo_info_length
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Linux kernel. Attackers reach the vulnerable code path via max_response without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Linux kernel. Attack surface: max_response / sensor_num / fifo_info_length.

🔥 Severity

Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Linux kernel を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details