CVE-2026-93190: platform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2a7a4e45a3aa4f4ef7013eb64649f6184b76a293, 4e37371cb4e3b8ff564d7760029236a7bd614562, 54d6b0ee9b8ba434089b11843effc111dc2e6ead.
Low priority for now. Upgrade to Linux Linux 2a7a4e45a3aa4f4ef7013eb64649f6184b76a293, 4e37371cb4e3b8ff564d7760029236a7bd614562, 54d6b0ee9b8ba434089b11843effc111dc2e6ead or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.1affected
- 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d and later · before 7617b210a2200b76d8f171819390468c7d189c80affected · git
- 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d and later · before 4e37371cb4e3b8ff564d7760029236a7bd614562affected · git
- 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d and later · before 2a7a4e45a3aa4f4ef7013eb64649f6184b76a293affected · git
- 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d and later · before e4728288473a5024a8bdba7d43f346719606fea0affected · git
- 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d and later · before 54d6b0ee9b8ba434089b11843effc111dc2e6eadaffected · git
- 348a2e8c93d3ca622cf1b293cd2f597c9db74d9d and later · before a0a8cd9fc9c48b95095bcec4b146f7a99486f58eaffected · git
- before 6.1not affected · semver
- 6.1.188 and later · up to and including 6.1.*not affected · semver
- 6.6.157 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93188Sep 17, 2026 · HID: roccat: bound device-supplied profile index0Monitor
- ← EarlierCVE-2026-93189Sep 17, 2026 · HID: core: quiesce input in hid_hw_stop() to prevent use-after-free35Monitor
- Later →CVE-2026-93191Sep 17, 2026 · smack: fix incorrect task context in smack_msg_queue_msgrcv0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2a7a4e45a3aa4f4ef7013eb64649f6184b76a293 | Vendor (CNA) |
| Linux Linux | 4e37371cb4e3b8ff564d7760029236a7bd614562 | Vendor (CNA) |
| Linux Linux | 54d6b0ee9b8ba434089b11843effc111dc2e6ead | Vendor (CNA) |
| Linux Linux | 7617b210a2200b76d8f171819390468c7d189c80 | Vendor (CNA) |
| Linux Linux | a0a8cd9fc9c48b95095bcec4b146f7a99486f58e | Vendor (CNA) |
| Linux Linux | e4728288473a5024a8bdba7d43f346719606fea0 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/4e37371cb4e3b8ff564d7760029236a7bd614562
- git.kernel.org/stable/c/54d6b0ee9b8ba434089b11843effc111dc2e6ead
- git.kernel.org/stable/c/7617b210a2200b76d8f171819390468c7d189c80
- git.kernel.org/stable/c/a0a8cd9fc9c48b95095bcec4b146f7a99486f58e
- git.kernel.org/stable/c/e4728288473a5024a8bdba7d43f346719606fea0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.