Answer in brief
CVE-2026-64329 records a Unknown severity vulnerability in usb: typec: ucsi: ccg: Fix use-after-free of ucsi on remove. 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.
Answer in brief
CVE-2026-64329 records a Unknown severity vulnerability in usb: typec: ucsi: ccg: Fix use-after-free of ucsi on remove. 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 | >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <f1adeb1ff8bef1467d6961059810795d02bbad5d || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <99381e762273a2410a3f0216000be32b013c0ea9 || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <1a160076d3d0dcd4a98a4599ad96eec0790b099b || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <c32df11147822d22facee8fa30c2e8971d12f426 || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <86c9ee928c4a370e323e432aaf8dca79c4ba7c85 || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <f5c772b76bbd95de8be51cf849c6098f6af6fcf9 || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <dbb500bad02146b388041877574829016591ddc8 || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <1f0bdc2884b67de337215079bba166df0cdf4ac5 | f1adeb1ff8bef1467d6961059810795d02bbad5d, 99381e762273a2410a3f0216000be32b013c0ea9, 1a160076d3d0dcd4a98a4599ad96eec0790b099b, c32df11147822d22facee8fa30c2e8971d12f426, 86c9ee928c4a370e323e432aaf8dca79c4ba7c85, f5c772b76bbd95de8be51cf849c6098f6af6fcf9, dbb500bad02146b388041877574829016591ddc8, 1f0bdc2884b67de337215079bba166df0cdf4ac5 |
| Linux/Linuxgeneric | 5.5 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: ccg: Fix use-after-free of ucsi on remove The threaded IRQ handler ccg_irq_handler() calls ucsi_notify_common(), which on a connector-change event calls ucsi_connector_change() and schedules connector work. In ucsi_ccg_remove(), ucsi_destroy() frees uc->ucsi (kfree) before free_irq() is called, so a handler invocation already in flight may access the freed object after ucsi_destroy(). CPU 0 (remove) | CPU 1 (threaded IRQ) ucsi_destroy(uc->ucsi) | ccg_irq_handler() kfree(ucsi) // FREE | ucsi_notify_common(uc->ucsi) // USE Move free_irq() before ucsi_destroy() in the remove path. It is kept after ucsi_unregister(): ucsi_unregister() cancels connector work whose handler issues GET_CONNECTOR_STATUS through ucsi_send_command_common(), which waits for a completion that is signalled from the IRQ handler, so the IRQ must stay active until that work has been cancelled. The probe error path already orders free_irq() before ucsi_destroy(). This bug was found by static analysis.
Quoted source text, attributed separately from HOL analysis.
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 | >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <f1adeb1ff8bef1467d6961059810795d02bbad5d || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <99381e762273a2410a3f0216000be32b013c0ea9 || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <1a160076d3d0dcd4a98a4599ad96eec0790b099b || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <c32df11147822d22facee8fa30c2e8971d12f426 || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <86c9ee928c4a370e323e432aaf8dca79c4ba7c85 || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <f5c772b76bbd95de8be51cf849c6098f6af6fcf9 || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <dbb500bad02146b388041877574829016591ddc8 || >=e32fd989ac1c45f993fbe89ad0a89aa9ea6993d2 <1f0bdc2884b67de337215079bba166df0cdf4ac5 | f1adeb1ff8bef1467d6961059810795d02bbad5d, 99381e762273a2410a3f0216000be32b013c0ea9, 1a160076d3d0dcd4a98a4599ad96eec0790b099b, c32df11147822d22facee8fa30c2e8971d12f426, 86c9ee928c4a370e323e432aaf8dca79c4ba7c85, f5c772b76bbd95de8be51cf849c6098f6af6fcf9, dbb500bad02146b388041877574829016591ddc8, 1f0bdc2884b67de337215079bba166df0cdf4ac5 |
| Linux/Linuxgeneric | 5.5 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: ccg: Fix use-after-free of ucsi on remove The threaded IRQ handler ccg_irq_handler() calls ucsi_notify_common(), which on a connector-change event calls ucsi_connector_change() and schedules connector work. In ucsi_ccg_remove(), ucsi_destroy() frees uc->ucsi (kfree) before free_irq() is called, so a handler invocation already in flight may access the freed object after ucsi_destroy(). CPU 0 (remove) | CPU 1 (threaded IRQ) ucsi_destroy(uc->ucsi) | ccg_irq_handler() kfree(ucsi) // FREE | ucsi_notify_common(uc->ucsi) // USE Move free_irq() before ucsi_destroy() in the remove path. It is kept after ucsi_unregister(): ucsi_unregister() cancels connector work whose handler issues GET_CONNECTOR_STATUS through ucsi_send_command_common(), which waits for a completion that is signalled from the IRQ handler, so the IRQ must stay active until that work has been cancelled. The probe error path already orders free_irq() before ucsi_destroy(). This bug was found by static analysis.
Quoted source text, attributed separately from HOL analysis.