Home

Description

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.

PUBLISHED Reserved 2025-06-18 | Published 2025-06-18 | Updated 2025-06-18 | Assigner Linux

Product status

Default status
unaffected

36ea23374d1f7b6a9d96a2b61d38830fdf23e45d (git) before 5ccb0420b7c9334ab8122037847101931b899301
affected

36ea23374d1f7b6a9d96a2b61d38830fdf23e45d (git) before 4bd9d5d20f344d015422969302d12653c903c271
affected

36ea23374d1f7b6a9d96a2b61d38830fdf23e45d (git) before 035ff33cf4db101250fb980a3941bf078f37a544
affected

Default status
affected

5.16
affected

Any version before 5.16
unaffected

5.18.18 (semver)
unaffected

5.19.2 (semver)
unaffected

6.0 (original_commit_for_fix)
unaffected

References

git.kernel.org/...c/5ccb0420b7c9334ab8122037847101931b899301

git.kernel.org/...c/4bd9d5d20f344d015422969302d12653c903c271

git.kernel.org/...c/035ff33cf4db101250fb980a3941bf078f37a544

cve.org (CVE-2022-50217)

nvd.nist.gov (CVE-2022-50217)

Download JSON