usb: typec: qcom-pmic-typec: disable cc_debounce_dwork on stop (CVE-2026-90027) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-90027

usb: typec: qcom-pmic-typec: disable cc_debounce_dwork on stop

Answer in brief

CVE-2026-90027 records a Unknown severity vulnerability in usb: typec: qcom-pmic-typec: disable cc_debounce_dwork on stop. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 16, 2026Updated Sep 16, 2026Source checked Sep 16, 2026First seen by HOL Sep 16, 2026Material review Sep 16, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=a4422ff221429c600c3dc5d0394fb3738b89d040 <4359b5f95c93a4658e08368fa6fab9d89eb98447 \|\| >=a4422ff221429c600c3dc5d0394fb3738b89d040 <c614d7c44ca7fb78867ba46b233acdb59287e8c8 \|\| >=a4422ff221429c600c3dc5d0394fb3738b89d040 <1ab669c2b44e1040ddfab7cd7f717aad580d17aa \|\| >=a4422ff221429c600c3dc5d0394fb3738b89d040 <263f7d61a4201cde16849b2d016251806e7418be	4359b5f95c93a4658e08368fa6fab9d89eb98447, c614d7c44ca7fb78867ba46b233acdb59287e8c8, 1ab669c2b44e1040ddfab7cd7f717aad580d17aa, 263f7d61a4201cde16849b2d016251806e7418be
Linux/Linuxgeneric	6.5	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 4359b5f95c93a4658e08368fa6fab9d89eb98447 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 16, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.