Answer in brief
CVE-2026-64594 records a Unknown severity vulnerability in usb: gadget: f_fs: initialize reset_work at allocation time. 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 | >=18d6b32fca3841f7cd9479b4024abd8a9b299281 <7fe895e0a9651518c4fc082487da770ff9c14c7f || >=18d6b32fca3841f7cd9479b4024abd8a9b299281 <0de6ebbabfbbc9c28350283dc97d8a519d5c6dd7 || >=18d6b32fca3841f7cd9479b4024abd8a9b299281 <cb19e54ebe9baf3c3243083ade65c937339ccb7b || >=18d6b32fca3841f7cd9479b4024abd8a9b299281 <d5631081be07f20e764d3cb5c98ac0a1004fba51 || >=18d6b32fca3841f7cd9479b4024abd8a9b299281 <c36393b0d14e1e9783888f821ffe29381b8f46dc || >=18d6b32fca3841f7cd9479b4024abd8a9b299281 <69faa3779250df14f51d5084f938a99809546e52 || >=18d6b32fca3841f7cd9479b4024abd8a9b299281 <ba1867999dbc4085e6d8c52ac5266005b8b2bf07 || >=18d6b32fca3841f7cd9479b4024abd8a9b299281 <3137b243c93982fe3460335e12f9247739766e10 | 7fe895e0a9651518c4fc082487da770ff9c14c7f, 0de6ebbabfbbc9c28350283dc97d8a519d5c6dd7, cb19e54ebe9baf3c3243083ade65c937339ccb7b, d5631081be07f20e764d3cb5c98ac0a1004fba51, c36393b0d14e1e9783888f821ffe29381b8f46dc, 69faa3779250df14f51d5084f938a99809546e52, ba1867999dbc4085e6d8c52ac5266005b8b2bf07, 3137b243c93982fe3460335e12f9247739766e10 |
| Linux/Linuxgeneric | 4.0 | Not reported |
Published upstream
Aug 6, 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 6, 2026
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: initialize reset_work at allocation time ffs_fs_kill_sb() unconditionally calls cancel_work_sync() on ffs->reset_work when a functionfs instance is unmounted: ffs_data_reset(ffs); cancel_work_sync(&ffs->reset_work); However ffs->reset_work is only ever initialized via INIT_WORK() in ffs_func_set_alt() and ffs_func_disable(), and only on the FFS_DEACTIVATED path. That state is reached solely by ffs_data_closed() when the instance is mounted with the "no_disconnect" option, so for the common case (no "no_disconnect", or mounted and unmounted without ever being deactivated) reset_work is never initialized. ffs_data_new() allocates the ffs_data with kzalloc_obj() and does not initialize reset_work, and ffs_data_reset()/ffs_data_clear() do not touch it either, so reset_work.func is left NULL. cancel_work_sync() on such a work then trips the WARN_ON(!work->func) guard in __flush_work(): WARNING: kernel/workqueue.c:4301 at __flush_work+0x330/0x360, CPU#3: umount Call trace: __flush_work cancel_work_sync ffs_fs_kill_sb [usb_f_fs] deactivate_locked_super deactivate_super cleanup_mnt __cleanup_mnt task_work_run exit_to_user_mode_loop el0_svc On older kernels cancel_work_sync() on a zero-initialized work struct was a silent no-op, which hid the missing initialization. Initialize reset_work once in ffs_data_new() so it is always valid for the lifetime of the ffs_data, and drop the now-redundant INIT_WORK() calls from the two deactivation paths.
Quoted source text, attributed separately from HOL analysis.