# CVE-2026-98758: usb: typec: ucsi: glink: fix use-after-free of ucsi on remove

> A use-after-free vulnerability in the Linux kernel's UCSI GLINK driver allows local attackers to execute arbitrary code or cause a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-108614, BELL-CVE-2026-98758, DEBIAN-CVE-2026-98758, GHSA-hvv7-vw9m-6v98, UBUNTU-CVE-2026-98758

## What is CVE-2026-98758?

CVE-2026-98758 is an use after free vulnerability in Linux, published on 18 Oct 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: ucsi: glink: fix use-after-free of ucsi on remove

The pmic_glink client is released by the devres cleanup, which runs
after pmic_glink_ucsi_remove() has returned, so its notification
callbacks can queue work until then. Work that runs after
ucsi_unregister() has been called touches freed state: it dereferences
the connector array that ucsi_unregister() freed, or registers and
unregisters the instance a second time.

Disable both work items with disable_work_sync() before unregistering,
and unregister only if the instance is still registered.

This issue was found by an in-house static analysis tool.

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


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

Apply the vendor's patch.

## Is CVE-2026-98758 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98758 is an use after free vulnerability in Linux, published on 18 Oct 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-98758 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-98758/ (Markdown: https://insights.sbomify.com/CVE-2026-98758/index.md)
```

## Sources

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

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