CVE-2022-50217

{"id": "CVE-2022-50217", "cveTags": [], "metrics": {}, "published": "2025-06-18T11:15:52.647", "references": [{"url": "https://git.kernel.org/stable/c/035ff33cf4db101250fb980a3941bf078f37a544", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/4bd9d5d20f344d015422969302d12653c903c271", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/5ccb0420b7c9334ab8122037847101931b899301", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Awaiting Analysis", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfuse: write inode in fuse_release()\n\nA race between write(2) and close(2) allows pages to be dirtied after\nfuse_flush -> write_inode_now().  If these pages are not flushed from\nfuse_release(), then there might not be a writable open file later.  So any\nremaining dirty pages must be written back before the file is released.\n\nThis is a partial revert of the blamed commit."}], "lastModified": "2025-06-18T13:47:40.833", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}