usb: gadget: f_fs: Fix Use-After-Free in AIO error path
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e78dcb1f7ec271449c54984dc90c62a5ba272de7, Kernel 0a2f71ccf9c2053de725e9a7922d081f3f3a3804, Kernel 153b5ecd29ed055562400bc17c91df3fd869b0ce and 8 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=de2080d41b5d584205e408d72021f0f335a046fc <e78dcb1f7ec271449c54984dc90c62a5ba272de7, >=de2080d41b5d584205e408d72021f0f335a046fc <0a2f71ccf9c2053de725e9a7922d081f3f3a3804, >=de2080d41b5d584205e408d72021f0f335a046fc <153b5ecd29ed055562400bc17c91df3fd869b0ce, >=de2080d41b5d584205e408d72021f0f335a046fc <4a2fb2d12b87b43724230abb52a1440617c7b6cc, >=de2080d41b5d584205e408d72021f0f335a046fc <922a29e1f8573fd405eea1a73a52112c4e7fcfc4, >=de2080d41b5d584205e408d72021f0f335a046fc <b5f0e80a03e87bd932487e03248eae3ba3ed7b45, =4.0 | e78dcb1f7ec271449c54984dc90c62a5ba272de7, 0a2f71ccf9c2053de725e9a7922d081f3f3a3804, 153b5ecd29ed055562400bc17c91df3fd869b0ce, 4a2fb2d12b87b43724230abb52a1440617c7b6cc, 922a29e1f8573fd405eea1a73a52112c4e7fcfc4, b5f0e80a03e87bd932487e03248eae3ba3ed7b45 |
| linux-kernel: Kernel | >=6.13.0 <6.18.51, >=6.19.0 <7.2.5, >=6.2.0 <6.6.160, >=6.7.0 <6.12.111, >=4.0.0 <6.1.191 | 6.18.51, 7.2.5, 6.6.160, 6.12.111, 6.1.191 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket