CVE-2026-90027
7.8 HIGHPublished 2026-09-16 · Updated 2026-09-16
AI risk analysis
- Summary
- This vulnerability allows for potential race conditions in the USB Type-C PMIC driver, which could lead to unauthorized operations if exploited.
- Exploitability
- Exploitation requires the attacker to have the ability to trigger the set_cc() and start_toggling() callbacks while the port_stop() is in progress, making it moderately difficult.
- Blast radius
- If exploited, this could result in unauthorized access or control over the USB Type-C port, potentially leading to data theft or system compromise.
- Detection
- No reliable host or network indicator is derivable from the published description.
- Prioritized remediation
- Upgrade to the fixed version 5.15.110 or later.
Analysis generated locally by qwen2.5:7b-instruct (no data left the box). AI-assisted — verify against primary sources before acting.
NVD 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.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
References
Data: NVD (public domain). Analysis: local $0 model. Defensive use only.