CVE-2026-63960

Kernel stack overwrite via malformed USB PD frame

Published Jul 19, 2026 · Updated Jul 19, 2026

Stack buffer overflow in the Linux kernel WCOVE USB Type-C driver allows physically proximate attackers to overwrite kernel stack memory via USB PD frames. wcove_read_rx_buffer() passes successive byte offsets in a 30-byte pd_message to regmap_read(), which writes four bytes per call, and also trusts a five-bit RX byte count that can reach 31. Reachability requires a WCOVE-controlled Type-C port and a connected USB PD partner; the published record establishes the overwrite but does not establish code execution or a specific service interruption.

CVSS severity3.5
Low
EPSS probability0.21%
Next 30 days · Sep 17, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Stack buffer overflow in the Linux kernel WCOVE USB Type-C driver allows physically proximate attackers to overwrite kernel stack memory via USB PD frames. wcove_read_rx_buffer() passes successive byte offsets in a 30-byte pd_message to regmap_read(), which writes four bytes per call, and also trusts a five-bit RX byte count that can reach 31. Reachability requires a WCOVE-controlled Type-C port and a connected USB PD partner; the published record establishes the overwrite but does not establish code execution or a specific service interruption.

The record

CVE
CVE-2026-63960
Published
Jul 19, 2026
Updated
Jul 19, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
T1200
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <5.10.259
  2. Affected versionversion=0 <5.15.210
  3. Affected versionversion=0 <6.1.176
  4. Affected versionversion=0 <6.12.93
  5. Affected versionversion=0 <6.18.35
  6. Affected versionversion=0 <6.6.143
  7. Affected versionversion=0 <7.0.12
  8. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3e632098d0521257ea965bbd6fde807d9bee5c8a
  9. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3f9d50c8b02b4af0646aa892465080f9061fc89c
  10. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4af7ad0e6d7aa4403dbb1dac7b9659b0421efcaa
  11. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5cd0e7ac4eefbdb330f8c72694fe74e63df65552
  12. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6899f5b6d7b83ce79a3d331dc61dd31bf73f9c22
  13. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d0e4b8b3c6b7607a16932556eaaca5d5cf69f192
  14. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e94933dc41b87503bf585c8c6d53d740620eceb9
  15. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f2a1edc0bd142edabc6c85d88713f2bc178dd317

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=0 <5.10.259; version=0 <5.15.210; version=0 <6.1.176; version=0 <6.12.93; version=0 <6.18.35; version=0 <6.6.143; version=0 <7.0.12; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3e632098d0521257ea965bbd6fde807d9bee5c8a; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3f9d50c8b02b4af0646aa892465080f9061fc89c; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4af7ad0e6d7aa4403dbb1dac7b9659b0421efcaa; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5cd0e7ac4eefbdb330f8c72694fe74e63df65552; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6899f5b6d7b83ce79a3d331dc61dd31bf73f9c22; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d0e4b8b3c6b7607a16932556eaaca5d5cf69f192; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e94933dc41b87503bf585c8c6d53d740620eceb9; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f2a1edc0bd142edabc6c85d88713f2bc178dd317

Published CVSS scores

3.5Amazon LinuxCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 11, 2026Sep 17, 2026
Latest reporting daySep 17, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1200Hardware Additions

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo