platform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count
Summary
| CVE | CVE-2026-93190 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-09-17 17:18:15 UTC |
|---|
| Updated | 2026-09-17 17:18:15 UTC |
|---|
| 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. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d 7617b210a2200b76d8f171819390468c7d189c80 git |
Not specified |
| CNA |
Linux |
Linux |
affected 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d 4e37371cb4e3b8ff564d7760029236a7bd614562 git |
Not specified |
| CNA |
Linux |
Linux |
affected 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d 2a7a4e45a3aa4f4ef7013eb64649f6184b76a293 git |
Not specified |
| CNA |
Linux |
Linux |
affected 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d e4728288473a5024a8bdba7d43f346719606fea0 git |
Not specified |
| CNA |
Linux |
Linux |
affected 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d 54d6b0ee9b8ba434089b11843effc111dc2e6ead git |
Not specified |
| CNA |
Linux |
Linux |
affected 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d a0a8cd9fc9c48b95095bcec4b146f7a99486f58e git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.1 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.188 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.157 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.110 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.52 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.6 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/4e37371cb4e3b8ff564d7760029236a7bd614562 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/7617b210a2200b76d8f171819390468c7d189c80 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/54d6b0ee9b8ba434089b11843effc111dc2e6ead |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/2a7a4e45a3aa4f4ef7013eb64649f6184b76a293 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a0a8cd9fc9c48b95095bcec4b146f7a99486f58e |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/e4728288473a5024a8bdba7d43f346719606fea0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.