Kernel memory corruption via unchecked connector index
Published Jul 19, 2026 · Updated Jul 19, 2026
Out-of-bounds access in Linux Kernel 4.13 through affected 7.0 releases allows attackers controlling a UCSI PPM to corrupt kernel memory. ucsi_connector_change() uses the notification's 7-bit connector number to index ucsi->connector[] and calls schedule_work() without validating the index against cap.num_connectors. Exploitation requires a buggy or malicious EC firmware or I2C-attached UCSI controller and drives a work-queue operation on memory beyond the connector array.
Summary
What happened
Out-of-bounds access in Linux Kernel 4.13 through affected 7.0 releases allows attackers controlling a UCSI PPM to corrupt kernel memory. ucsi_connector_change() uses the notification's 7-bit connector number to index ucsi->connector[] and calls schedule_work() without validating the index against cap.num_connectors. Exploitation requires a buggy or malicious EC firmware or I2C-attached UCSI controller and drives a work-queue operation on memory beyond the connector array.
The record
- CVE
- CVE-2026-63958
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=0 <6.1.176
- Affected versionversion=0 <6.12.93
- Affected versionversion=0 <6.18.35
- Affected versionversion=0 <6.6.143
- Affected versionversion=0 <7.0.12
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0edd1e21587b0483c7ceb993b9fb9668bbef7433
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <156b6f0aec6108909b0c4aedc78865b12766b347
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <288a81a8507052bcfbf884d39a463c44c42c5fd9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5af2719b460ab904c504fc069d1dd2a3aa2b22b0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bd24d92af4ae021b6209f28e9a57e1bf2260d4fd
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cea949203faef9cb783adc7b978cce056271e057
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
No sourced classifications are available.
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