usb: gadget: f_fs: Fix Use-After-Free in AIO error path
CVE-2026-90044 · published 16 Sept 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-90044?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: de2080d41b5d584205e408d72021f0f335a046fc to < 0a2f71ccf9c2053de725e9a7922d081f3f3a3804, de2080d41b5d584205e408d72021f0f335a046fc to < b5f0e80a03e87bd932487e03248eae3ba3ed7b45, de2080d41b5d584205e408d72021f0f335a046fc to < 153b5ecd29ed055562400bc17c91df3fd869b0ce, de2080d41b5d584205e408d72021f0f335a046fc to < 4a2fb2d12b87b43724230abb52a1440617c7b6cc
- Linux Linux: 4.0
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: f_fs: Fix Use-After-Free in AIO error path
In ffs_epfile_write_iter() and ffs_epfile_read_iter(), when ffs_epfile_io()
fails with an error other than -EIOCBQUEUED, the io_data structure (`p`) is
freed. However, for AIO operations, the kiocb cancel function was already
armed and kiocb->private was set to `p`.
If a concurrent cancel operation (such as sys_io_cancel()) executes after
ffs_epfile_io() fails but before the function frees `p`, a Use-After-Free
can occur when the cancellation handler accesses the freed pointer.
To securely fix this race condition, we must properly un-arm the
cancellation. Invoking `kiocb->ki_complete()` does exactly this by
acquiring `ctx->ctx_lock` and safely removing the kiocb from the active
sequence. In doing so, it ensures that a parallel io_cancel can no longer
discover the kiocb, effectively closing the race window.
We then return -EIOCBQUEUED to notify the VFS layer that the kiocb has been
consumed and it should avoid attempting to complete the request again or
triggering subsequent completion handlers.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/0a2f71ccf9c2053de725e9a7922d081f3f3a3804
- git.kernel.org/stable/c/b5f0e80a03e87bd932487e03248eae3ba3ed7b45
- git.kernel.org/stable/c/153b5ecd29ed055562400bc17c91df3fd869b0ce
- git.kernel.org/stable/c/4a2fb2d12b87b43724230abb52a1440617c7b6cc
- git.kernel.org/stable/c/e78dcb1f7ec271449c54984dc90c62a5ba272de7
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON