CVE-2026-63960: usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer()
Noroxi assessment
Priority: Monitor (action score 22/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.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 3e632098d0521257ea965bbd6fde807d9bee5c8a, 3f9d50c8b02b4af0646aa892465080f9061fc89c, 4af7ad0e6d7aa4403dbb1dac7b9659b0421efcaa.
Low priority for now. Upgrade to Linux Linux 3e632098d0521257ea965bbd6fde807d9bee5c8a, 3f9d50c8b02b4af0646aa892465080f9061fc89c, 4af7ad0e6d7aa4403dbb1dac7b9659b0421efcaa 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: usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer() wcove_read_rx_buffer() copies the PD RX FIFO into the caller's struct pd_message with for (i = 0; i < USBC_RXINFO_RXBYTES(info); i++) regmap_read(wcove->regmap, USBC_RX_DATA + i, msg + i); which has two problems: USBC_RXINFO_RXBYTES() is a 5-bit field (max 31) while struct pd_message is 30 bytes (__le16 header + __le32 payload[PD_MAX_PAYLOAD], packed). The byte count latched in RXINFO is the number of bytes the port partner put on the wire, so a malicious partner that transmits a 31-byte frame can drive the loop one byte past the destination if the WCOVE BMC receiver does not enforce the PD object-count limit in hardware. The existing FIXME flagged this as unverified. Independently, regmap_read() takes an unsigned int * and stores a full unsigned int at the destination. Passing the byte pointer msg + i means each iteration writes four bytes; the high three are zero (val_bits is 8) and are normally overwritten by the next iteration, but the final iteration's high bytes are not. With RXBYTES == 30 the i == 29 iteration already writes three zero bytes past msg, which sits on the IRQ thread's stack in wcove_typec_irq(). Clamp the loop to sizeof(struct pd_message) and read each register into a local before storing only its low byte, so the copy can never exceed the destination regardless of what RXINFO reports.
- Published
- Jul 19, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Is your version affected? Check itNoroxi 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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
- 4.15affected
- 3c4fb9f169214290ec9a943907321e6265b36f65 and later · before 3e632098d0521257ea965bbd6fde807d9bee5c8aaffected · git
- 3c4fb9f169214290ec9a943907321e6265b36f65 and later · before f2a1edc0bd142edabc6c85d88713f2bc178dd317affected · git
- 3c4fb9f169214290ec9a943907321e6265b36f65 and later · before 6899f5b6d7b83ce79a3d331dc61dd31bf73f9c22affected · git
- 3c4fb9f169214290ec9a943907321e6265b36f65 and later · before 5cd0e7ac4eefbdb330f8c72694fe74e63df65552affected · git
- 3c4fb9f169214290ec9a943907321e6265b36f65 and later · before d0e4b8b3c6b7607a16932556eaaca5d5cf69f192affected · git
- 3c4fb9f169214290ec9a943907321e6265b36f65 and later · before e94933dc41b87503bf585c8c6d53d740620eceb9affected · git
- 3c4fb9f169214290ec9a943907321e6265b36f65 and later · before 3f9d50c8b02b4af0646aa892465080f9061fc89caffected · git
- 3c4fb9f169214290ec9a943907321e6265b36f65 and later · before 4af7ad0e6d7aa4403dbb1dac7b9659b0421efcaaaffected · git
- before 4.15not affected · semver
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.15 and later · before 5.10.259
- linux linux kernel5.11 and later · before 5.15.210
- linux linux kernel5.16 and later · before 6.1.176
- linux linux kernel6.2 and later · before 6.6.143
- linux linux kernel6.7 and later · before 6.12.93
- linux linux kernel6.13 and later · before 6.18.35
- linux linux kernel6.19 and later · before 7.0.12
- linux linux kernel7.1
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.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.12-1 | 7.0.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-63958Jul 19, 2026 · usb: typec: ucsi: validate connector number in ucsi_connector_change()22Monitor
- ← EarlierCVE-2026-63959Jul 19, 2026 · usb: typec: tcpm/tcpci_maxim: validate header NDO against RX_BYTE_CNT22Monitor
- Later →CVE-2026-63961Jul 19, 2026 · usb: typec: altmodes/displayport: validate count before reading Status Update VDO22Monitor
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 | 3e632098d0521257ea965bbd6fde807d9bee5c8a | Vendor (CNA) |
| Linux Linux | 3f9d50c8b02b4af0646aa892465080f9061fc89c | Vendor (CNA) |
| Linux Linux | 4af7ad0e6d7aa4403dbb1dac7b9659b0421efcaa | Vendor (CNA) |
| Linux Linux | 5cd0e7ac4eefbdb330f8c72694fe74e63df65552 | Vendor (CNA) |
| Linux Linux | 6899f5b6d7b83ce79a3d331dc61dd31bf73f9c22 | Vendor (CNA) |
| Linux Linux | d0e4b8b3c6b7607a16932556eaaca5d5cf69f192 | Vendor (CNA) |
| Linux Linux | e94933dc41b87503bf585c8c6d53d740620eceb9 | Vendor (CNA) |
| Linux Linux | f2a1edc0bd142edabc6c85d88713f2bc178dd317 | Vendor (CNA) |
| debian:linux | 6.1.176-1 · 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).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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
- CVSS— → 5.5
- Severity— → medium
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3f9d50c8b02b4af0646aa892465080f9061fc89c
- git.kernel.org/stable/c/4af7ad0e6d7aa4403dbb1dac7b9659b0421efcaa
- git.kernel.org/stable/c/5cd0e7ac4eefbdb330f8c72694fe74e63df65552
- git.kernel.org/stable/c/6899f5b6d7b83ce79a3d331dc61dd31bf73f9c22
- git.kernel.org/stable/c/d0e4b8b3c6b7607a16932556eaaca5d5cf69f192
- git.kernel.org/stable/c/e94933dc41b87503bf585c8c6d53d740620eceb9
- git.kernel.org/stable/c/f2a1edc0bd142edabc6c85d88713f2bc178dd317
Vendor advisories and official records. Exploit/PoC links are deliberately left out.