CVE-2026-64463
Received Received - Intake

USB Type-C TCPCI Port Unregister Flaw in Linux Kernel

Vulnerability report for CVE-2026-64463, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-25

Last updated on: 2026-07-27

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpci_rt1711h: unregister TCPCI port with devres rt1711h_probe() registers the TCPCI port before requesting the interrupt and enabling alert interrupts. If either of those later steps fails, the probe function returns without unregistering the TCPCI port. The explicit unregister currently only happens from the remove callback. Register a devres action immediately after tcpci_register_port() succeeds, so tcpci_unregister_port() runs on later probe failures and on driver detach. Drop the remove callback to avoid unregistering the same port twice. This issue was identified during our ongoing static-analysis research while reviewing kernel code.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-25
Last Modified
2026-07-27
Generated
2026-08-14
AI Q&A
2026-07-25
EPSS Evaluated
2026-08-13
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves improper handling of TCPCI port registration in the rt1711h_probe function. The probe function registers the TCPCI port before completing all required setup steps like requesting interrupts and enabling alerts. If any of these later steps fail, the probe function exits without properly unregistering the port, leaving it registered. Normally, unregistering only occurs in the remove callback, which may not be triggered if the probe fails.

Detection Guidance

This vulnerability is specific to the Linux kernel's USB Type-C TCPM driver (tcpci_rt1711h) and does not have network-based detection methods. To check if your system is affected, verify the kernel version and whether the tcpci_rt1711h driver is loaded. Use commands like 'uname -r' to check the kernel version and 'lsmod | grep tcpci' to see if the driver is loaded.

Impact Analysis

This vulnerability could lead to resource leaks in the Linux kernel, where a TCPCI port remains registered even after the driver fails to initialize properly. This may cause system instability or unexpected behavior in USB Type-C functionality, potentially disrupting connected devices or power delivery.

Compliance Impact

This vulnerability does not directly affect compliance with standards like GDPR or HIPAA as it is a Linux kernel driver issue related to improper resource cleanup during probe failures. It does not involve data exposure or privacy violations that would typically trigger such compliance concerns.

Mitigation Strategies

Apply the latest kernel update from your Linux distribution to ensure the fix is included. If you are running a vulnerable kernel version, update immediately. Monitor kernel release notes for patches addressing CVE-2026-64463. No immediate manual mitigation is required beyond updating the kernel.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-64463. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart