CVE-2026-64594

Not scored yetLast modified Aug 17, 2026

Description

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.

Metrics

No CVSS score has been published yet.

Affected software

Source: the vendor's advisory (CNA). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 18d6b32fca3841f7cd9479b4024abd8a9b299281, < 7fe895e0a9651518c4fc082487da770ff9c14c7f; >= 18d6b32fca3841f7cd9479b4024abd8a9b299281, < 0de6ebbabfbbc9c28350283dc97d8a519d5c6dd7; >= 18d6b32fca3841f7cd9479b4024abd8a9b299281, < cb19e54ebe9baf3c3243083ade65c937339ccb7b; >= 18d6b32fca3841f7cd9479b4024abd8a9b299281, < d5631081be07f20e764d3cb5c98ac0a1004fba51; >= 18d6b32fca3841f7cd9479b4024abd8a9b299281, < c36393b0d14e1e9783888f821ffe29381b8f46dc; >= 18d6b32fca3841f7cd9479b4024abd8a9b299281, < 69faa3779250df14f51d5084f938a99809546e52; >= 18d6b32fca3841f7cd9479b4024abd8a9b299281, < ba1867999dbc4085e6d8c52ac5266005b8b2bf07; >= 18d6b32fca3841f7cd9479b4024abd8a9b299281, < 3137b243c93982fe3460335e12f9247739766e10
LinuxLinux4.0

References

Timeline

Published
Aug 6, 2026
Last modified
Aug 17, 2026
NVD status
Received

Related CVEs from 2026

CVE-2026-64595In the Linux kernel, the following vulnerability has been resolved: HID: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove() hid_gCVE-2026-64596In the Linux kernel, the following vulnerability has been resolved: libfs: set SB_I_NOEXEC and SB_I_NODEV by default in init_pseudo() SincCVE-2026-645979.8In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_close() replay A response-bearingCVE-2026-645988.8In the Linux kernel, the following vulnerability has been resolved: smb/client: Fix error code in smb2_aead_req_alloc() The "*num_sgs" varCVE-2026-645997.8In the Linux kernel, the following vulnerability has been resolved: crypto: amlogic - avoid double cleanup in meson_crypto_probe() When meCVE-2026-64608.8Type confusion in PostgreSQL allows an object creator to execute arbitrary code as the operating system user running the database, via ALTERCVE-2026-646007.8In the Linux kernel, the following vulnerability has been resolved: xfs: resample the data fork mapping after cycling ILOCK xfs_reflink_fiCVE-2026-646017.8In the Linux kernel, the following vulnerability has been resolved: ALSA: us144mkii: capture_urb_complete: redundant usb_anchor_urb corruptCVE-2026-64602In the Linux kernel, the following vulnerability has been resolved: iio: adc: spear: Initialize completion before requesting IRQ In the reCVE-2026-64603In the Linux kernel, the following vulnerability has been resolved: platform/x86: intel-hid: Protect ACPI notify handler against recursion CVE-2026-64604In the Linux kernel, the following vulnerability has been resolved: KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest mCVE-2026-646069.8Deserialization of untrusted data vulnerability that may allow class-registration checks to be bypassed during Java lambda deserialization.
CVE-2026-64594: Unscored | Vulnix