# CVE-2026-64463: usb: typec: tcpci_rt1711h: unregister TCPCI port with devres

> A memory leak in the Linux kernel's RT1711H USB Type-C driver can lead to resource exhaustion and denial of service if probe operations fail.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-64463, DEBIAN-CVE-2026-64463, GHSA-fcgc-c7jf-cmfv, ROOT-OS-DEBIAN-12-CVE-2026-64463, ROOT-OS-UBUNTU-2204-CVE-2026-64463, UBUNTU-CVE-2026-64463

## What is CVE-2026-64463?

CVE-2026-64463 is a high-severity memory corruption vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2026-64463?


## How do I fix CVE-2026-64463?

Apply the vendor's patch.

## Is CVE-2026-64463 being exploited?

There is no known exploitation of CVE-2026-64463 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64463 and fix it if it is affected.

What it is: CVE-2026-64463 is a high-severity memory corruption vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64463 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64463/ (Markdown: https://insights.sbomify.com/CVE-2026-64463/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64463
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64463
- OSV: https://osv.dev/vulnerability/CVE-2026-64463

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64463/
Summaries are generated and may contain mistakes; the official description above is the record.