Answer in brief
CVE-2026-89737 records a Unknown severity vulnerability in usb: typec: thunderbolt: Disable work before freeing tbt 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 | >=100e257386595b3f1865ca8a991e2ba74f9701ff <ebb840d982a612261cfc8a7687735a140c6c7024 || >=100e257386595b3f1865ca8a991e2ba74f9701ff <0a25484fe22f621e151367a59a82330a22ac80bc || >=100e257386595b3f1865ca8a991e2ba74f9701ff <92090f6ff2acc81e9dd99881dcfb4f8c1bdaabd3 | ebb840d982a612261cfc8a7687735a140c6c7024, 0a25484fe22f621e151367a59a82330a22ac80bc, 92090f6ff2acc81e9dd99881dcfb4f8c1bdaabd3 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: usb: typec: thunderbolt: Disable work before freeing tbt on remove tbt_altmode_remove() drops the plug and cable references without draining tbt->work. The work function dereferences those references, and can also requeue itself in its error path. The VDM callbacks can queue the same work item. Disable and drain tbt->work before dropping the references. This waits for an existing invocation and prevents subsequent schedule_work() calls from queueing it during teardown. This issue was found by an in-house static analysis tool and confirmed by manual code review.
Quoted source text, attributed separately from HOL analysis.