# CVE-2026-90027: usb: typec: qcom-pmic-typec: disable cc_debounce_dwork on stop

> A use-after-free vulnerability in the Linux kernel's Qualcomm PMIC Type-C driver allows attackers to cause denial of service or execute code via race conditions during port stop.

- **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:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101666, BELL-CVE-2026-90027, DEBIAN-CVE-2026-90027, GHSA-fm22-hcrq-m39w, UBUNTU-CVE-2026-90027

## What is CVE-2026-90027?

CVE-2026-90027 is a high-severity use after free vulnerability in Linux, published on 16 Sep 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: qcom-pmic-typec: disable cc_debounce_dwork on stop

cc_debounce_dwork is queued from the set_cc() and start_toggling()
callbacks, which run from TCPM's kthread worker.  port_stop() returns
before tcpm_unregister_port() destroys that worker.  Flushing the worker
during unregister may therefore run a callback which queues the delayed
work after port_stop() has returned.

The delayed work can then run after devres has freed pmic_typec_port.

Use disable_delayed_work_sync() in port_stop() to cancel a pending
instance and prevent the TCPM callbacks from queueing another one.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-90027 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90027 is a high-severity use after free vulnerability in Linux, published on 16 Sep 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-90027 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-90027/ (Markdown: https://insights.sbomify.com/CVE-2026-90027/index.md)
```

## Sources

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

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