Menu

Star on GitHub · 3.2k

CVE-2026-63958

In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: validate connector number in ucsi_connector_change() The connector number in a UCSI CCI notification is a 7-b…

Published Jul 19, 2026EPSS 0.21%

Overview

CVE-2026-63958 is a known-severity vulnerability. It was published on July 19, 2026.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

usb: typec: ucsi: validate connector number in ucsi_connector_change()

The connector number in a UCSI CCI notification is a 7-bit field

supplied by the PPM. ucsi_connector_change() uses it to index the

ucsi->connector[] array without checking it against the number of

connectors the PPM reported at init time, so a buggy or malicious PPM

(EC firmware, or an I2C-attached UCSI controller on the ccg / stm32g0 /

glink transports) can drive schedule_work() on memory past the end of

the array.

Reject connector numbers that are zero or exceed cap.num_connectors

before dereferencing the array.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-63958?

CVE-2026-63958 is a known-severity vulnerability. It was published on July 19, 2026.

How severe is CVE-2026-63958?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-63958?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-63958?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-63958 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.