fuse: write inode in fuse_release()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
5.18.185.19.26.0In 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.
From the CVE record · Linux
A race between write(2) and close(2) in the Linux kernel’s FUSE handling can dirty pages after an inode write. If the remaining pages are not written back before the file is released, there may be no writable open file later to flush them. The input does not specify attacker access or authentication requirements.
Engineers running Linux kernels with FUSE should check their exposure; affected versions are not specified.