Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64594: usb: gadget: f_fs: initialize reset_work at allocation time

—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Fixed version: Linux Linux 0de6ebbabfbbc9c28350283dc97d8a519d5c6dd7, 3137b243c93982fe3460335e12f9247739766e10, 69faa3779250df14f51d5084f938a99809546e52.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0de6ebbabfbbc9c28350283dc97d8a519d5c6dd7, 3137b243c93982fe3460335e12f9247739766e10, 69faa3779250df14f51d5084f938a99809546e52 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Aug 6, 2026
Updated
Aug 17, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64594

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.0affected
    • 18d6b32fca3841f7cd9479b4024abd8a9b299281 and later · before 7fe895e0a9651518c4fc082487da770ff9c14c7faffected · git
    • 18d6b32fca3841f7cd9479b4024abd8a9b299281 and later · before 0de6ebbabfbbc9c28350283dc97d8a519d5c6dd7affected · git
    • 18d6b32fca3841f7cd9479b4024abd8a9b299281 and later · before cb19e54ebe9baf3c3243083ade65c937339ccb7baffected · git
    • 18d6b32fca3841f7cd9479b4024abd8a9b299281 and later · before d5631081be07f20e764d3cb5c98ac0a1004fba51affected · git
    • 18d6b32fca3841f7cd9479b4024abd8a9b299281 and later · before c36393b0d14e1e9783888f821ffe29381b8f46dcaffected · git
    • 18d6b32fca3841f7cd9479b4024abd8a9b299281 and later · before 69faa3779250df14f51d5084f938a99809546e52affected · git
    • 18d6b32fca3841f7cd9479b4024abd8a9b299281 and later · before ba1867999dbc4085e6d8c52ac5266005b8b2bf07affected · git
    • 18d6b32fca3841f7cd9479b4024abd8a9b299281 and later · before 3137b243c93982fe3460335e12f9247739766e10affected · git
    • before 4.0not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.4-17.1.4-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-64591Aug 6, 2026 · iommu/vt-d: Avoid WARNING in sva unbind path
    0Monitor
  • ← EarlierCVE-2026-64592Aug 6, 2026 · riscv: mm: Unconditionally sfence.vma for spurious fault
    0Monitor
  • Later →CVE-2026-64595Aug 6, 2026 · HID: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove()
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0de6ebbabfbbc9c28350283dc97d8a519d5c6dd7Vendor (CNA)
Linux Linux3137b243c93982fe3460335e12f9247739766e10Vendor (CNA)
Linux Linux69faa3779250df14f51d5084f938a99809546e52Vendor (CNA)
Linux Linux7fe895e0a9651518c4fc082487da770ff9c14c7fVendor (CNA)
Linux Linuxba1867999dbc4085e6d8c52ac5266005b8b2bf07Vendor (CNA)
Linux Linuxc36393b0d14e1e9783888f821ffe29381b8f46dcVendor (CNA)
Linux Linuxcb19e54ebe9baf3c3243083ade65c937339ccb7bVendor (CNA)
Linux Linuxd5631081be07f20e764d3cb5c98ac0a1004fba51Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records