---
id: "CVE-2026-98758"
kind: "vulnerability"
aliases: ["CVE-2026-98758"]
title: "Linux kernel: USB Type-C UCSI driver use-after-free on device removal"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["linux-kernel", "qualcomm-arm", "runtime", "usb-typec"]
not_affected_if: ["no-pmic-glink-hardware"]
published_at: "2026-10-18T16:17:29+00:00"
first_seen_at: "2026-10-23T21:57:16+00:00"
updated_at: "2026-10-25T05:16:49+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98758", "first_seen_at": "2026-10-23T21:57:16+00:00"}]
---

# Linux kernel: USB Type-C UCSI driver use-after-free on device removal

In the Linux kernel's UCSI USB Type-C driver for Qualcomm pmic_glink, queued work can run after the connector state has been freed during device removal. The sources describe this as a use-after-free that can touch freed memory, and do not state a demonstrated code execution path.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `uname -r` and compare against the fixed kernel build listed by your distribution's advisory.
- Check whether the `ucsi_glink` or `pmic_glink_ucsi` driver is loaded with `lsmod | grep -i ucsi`.
- unknown

## Fix

- Update the Linux kernel to a release that includes the upstream commit fixing the UCSI glink use-after-free (fixed version: unknown).
- unknown

## Timeline

- 2026-10-23T21:57:16+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98758

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_