Answer in brief
CVE-2026-90026 records a Unknown severity vulnerability in usb: typec: qcom-pmic: cancel reset_work 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.
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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a4422ff221429c600c3dc5d0394fb3738b89d040 <0b69b166852dbf1f9532b22bd49f502e5970eb95 || >=a4422ff221429c600c3dc5d0394fb3738b89d040 <b9a7eed472edbfa8dec0fdeafd5e796550a8a8b7 || >=a4422ff221429c600c3dc5d0394fb3738b89d040 <d4e00a1eb39174e25ef759b8fb1111bba8e87b1e || >=a4422ff221429c600c3dc5d0394fb3738b89d040 <52d556f08547733948cc40b8b11e6b68dccee7b2 || >=a4422ff221429c600c3dc5d0394fb3738b89d040 <7b0df6efd143f8085bdb68778a013a46f1349913 | 0b69b166852dbf1f9532b22bd49f502e5970eb95, b9a7eed472edbfa8dec0fdeafd5e796550a8a8b7, d4e00a1eb39174e25ef759b8fb1111bba8e87b1e, 52d556f08547733948cc40b8b11e6b68dccee7b2, 7b0df6efd143f8085bdb68778a013a46f1349913 |
| Linux/Linuxgeneric | 6.5 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
In the Linux kernel, the following vulnerability has been resolved: usb: typec: qcom-pmic: cancel reset_work on stop pdphy_stop() disables IRQs but leaves reset_work pending. If the IRQ handler schedules it just before disable_irq(), the work runs after remove() frees the struct via devm. Call cancel_work_sync() after disabling IRQs to close the window. This issue was found by an in-house static analysis tool.
Quoted source text, attributed separately from HOL analysis.