CVE-2026-93190platform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count
- 8.4HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 32 days later
· 32 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.4 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.4 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.4.
Affected products
- affected 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d – < 7617b210a2200b76d8f171819390468c7d189c80
- affected 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d – < 4e37371cb4e3b8ff564d7760029236a7bd614562
- affected 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d – < 2a7a4e45a3aa4f4ef7013eb64649f6184b76a293
- affected 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d – < e4728288473a5024a8bdba7d43f346719606fea0
- affected 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d – < 54d6b0ee9b8ba434089b11843effc111dc2e6ead
- affected 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d – < a0a8cd9fc9c48b95095bcec4b146f7a99486f58e
- affected 6.1
- unaffected < 6.1
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/7617b210a2200b76d8f171819390468c7d189c80 (opens in a new tab)
- https://git.kernel.org/stable/c/4e37371cb4e3b8ff564d7760029236a7bd614562 (opens in a new tab)
- https://git.kernel.org/stable/c/2a7a4e45a3aa4f4ef7013eb64649f6184b76a293 (opens in a new tab)
- https://git.kernel.org/stable/c/e4728288473a5024a8bdba7d43f346719606fea0 (opens in a new tab)
- https://git.kernel.org/stable/c/54d6b0ee9b8ba434089b11843effc111dc2e6ead (opens in a new tab)
- https://git.kernel.org/stable/c/a0a8cd9fc9c48b95095bcec4b146f7a99486f58e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82298 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93190)Record last updated .