# CVE-2026-98759: usb: typec: tipd: fix uninitialized typec_partner_desc in cd321x_update_work()

> An attacker with physical access can trigger uninitialized memory usage in the Linux kernel USB Type-C driver, potentially leaking stack data or executing arbitrary code.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98759, DEBIAN-CVE-2026-98759, GHSA-34hh-4678-7488, UBUNTU-CVE-2026-98759

## What is CVE-2026-98759?

CVE-2026-98759 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

usb: typec: tipd: fix uninitialized typec_partner_desc in cd321x_update_work()

cd321x_update_work() passes a stack-allocated typec_partner_desc to
typec_register_partner() after initializing only usb_pd, accessory and
identity.

typec_register_partner() copies attach and deattach from the descriptor
into the partner. With those fields left unset, garbage function pointers
may be stored and later invoked from typec_partner_link_device() when a USB
device is linked to the port. Uninitialized pd_revision and usb_capability
similarly leak stack data through partner sysfs.

Zero-initialize the descriptor so optional callbacks remain NULL and the
remaining fields are zero.

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


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

Apply the vendor's patch.

## Is CVE-2026-98759 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98759 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-98759 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-98759/ (Markdown: https://insights.sbomify.com/CVE-2026-98759/index.md)
```

## Sources

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

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