fuse: write inode in fuse_release()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 035ff33cf4db101250fb980a3941bf078f37a544, Kernel 4bd9d5d20f344d015422969302d12653c903c271 and Kernel 5ccb0420b7c9334ab8122037847101931b899301.
In the Linux kernel, the following vulnerability has been resolved: fuse: write inode in fuse_release() A race between write(2) and close(2) allows pages to be dirtied after fuse_flush -> write_inode_now(). If these pages are not flushed from fuse_release(), then there might not be a writable open file later. So any remaining dirty pages must be written back before the file is released. This is a partial revert of the blamed commit.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.16, >=36ea23374d1f7b6a9d96a2b61d38830fdf23e45d <035ff33cf4db101250fb980a3941bf078f37a544, >=36ea23374d1f7b6a9d96a2b61d38830fdf23e45d <4bd9d5d20f344d015422969302d12653c903c271, >=36ea23374d1f7b6a9d96a2b61d38830fdf23e45d <5ccb0420b7c9334ab8122037847101931b899301 | 035ff33cf4db101250fb980a3941bf078f37a544, 4bd9d5d20f344d015422969302d12653c903c271, 5ccb0420b7c9334ab8122037847101931b899301 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket