Answer in brief
CVE-2026-98758 records a Unknown severity vulnerability in usb: typec: ucsi: glink: 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 | >=62b5412b1f4afab27d8df90ddcabb8e1e11a00ad <432b58cd959e594909a581b4974396cdbc9d4ca1 || >=62b5412b1f4afab27d8df90ddcabb8e1e11a00ad <41934f92e7a54d4080ac0b17aacc83224946785c || >=62b5412b1f4afab27d8df90ddcabb8e1e11a00ad <ee8577de01c6b6c7dd1d76b52242c54d37a989f4 || >=62b5412b1f4afab27d8df90ddcabb8e1e11a00ad <63b269ec537dc0fd26d0bd64872c26860d108c9d | 432b58cd959e594909a581b4974396cdbc9d4ca1, 41934f92e7a54d4080ac0b17aacc83224946785c, ee8577de01c6b6c7dd1d76b52242c54d37a989f4, 63b269ec537dc0fd26d0bd64872c26860d108c9d |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: glink: fix use-after-free of ucsi on remove The pmic_glink client is released by the devres cleanup, which runs after pmic_glink_ucsi_remove() has returned, so its notification callbacks can queue work until then. Work that runs after ucsi_unregister() has been called touches freed state: it dereferences the connector array that ucsi_unregister() freed, or registers and unregisters the instance a second time. Disable both work items with disable_work_sync() before unregistering, and unregister only if the instance is still registered. This issue was found by an in-house static analysis tool.
Quoted source text, attributed separately from HOL analysis.