PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-93190 Linux CVE debrief

A buffer overflow vulnerability was found in the Linux kernel's platform/chrome cros_ec_typec module. The function cros_typec_register_partner_pdos() does not validate the source_cap_count and sink_cap_count fields from the EC TYPEC_STATUS response, which can lead to a stack-based buffer overflow if either count is larger than 7. This issue can result in potential code execution and security issues if exploited. Linux kernel developers and maintainers should prioritize validating PDO counts to prevent buffer overflow and fix this vulnerability.

Vendor
Linux
Product
Unknown
CVSS
HIGH 8.4
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

Linux kernel developers and maintainers, ChromeOS developers and maintainers, and users of Linux kernel versions affected by this vulnerability, as well as security teams and operators responsible for maintaining and securing Linux-based systems. These groups should prioritize validating PDO counts and implementing necessary fixes to prevent buffer overflow and potential code execution.

Why it matters

A buffer overflow vulnerability in the Linux kernel's platform/chrome cros_ec_typec module can lead to potential code execution and security issues. Linux kernel developers and maintainers should validate PDO counts to prevent buffer overflow and fix this vulnerability.

  • Buffer overflow can lead to stack corruption and potential code execution
  • Validation of PDO counts is necessary to prevent buffer overflow
  • Fixing this vulnerability is crucial for maintaining the security of the Linux kernel

Technical summary

The Linux kernel's platform/chrome cros_ec_typec module has a buffer overflow vulnerability. The function cros_typec_register_partner_pdos() copies partner PDOs from the EC TYPEC_STATUS response into a fixed-size array without validating the source_cap_count and sink_cap_count fields. This can lead to a stack-based buffer overflow if either count is larger than 7, potentially resulting in code execution. Compliant ChromeOS EC firmware caps these counts, but the kernel should still validate them to ensure security. Affected Linux kernel versions should be updated with a fix.

Defensive priority

High

Recommended defensive actions

  • Validate source_cap_count and sink_cap_count fields in cros_typec_register_partner_pdos()
  • Implement bounds checking for PDO counts
  • Update Linux kernel to version with fix
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • 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 Linux kernel's platform/chrome cros_ec_typec module has a buffer overflow vulnerability. The function cros_typec_register_partner_pdos() copies partner PDOs from the EC TYPEC_STATUS response into a fixed-size array without validating the source_cap_count and sink_cap_count fields. Compliant ChromeOS EC firmware caps these counts, but the kernel should still validate them.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-93190 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-93190

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-93190 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-93190

    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/2a7a4e45a3aa4f4ef7013eb64649f6184b76a293

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/4e37371cb4e3b8ff564d7760029236a7bd614562

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/54d6b0ee9b8ba434089b11843effc111dc2e6ead

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/7617b210a2200b76d8f171819390468c7d189c80

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a0a8cd9fc9c48b95095bcec4b146f7a99486f58e

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/e4728288473a5024a8bdba7d43f346719606fea0

    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.