ghsa-f5r8-w4hp-7v3r
Vulnerability from github
Published
2025-06-18 12:30
Modified
2025-06-18 12:30
Details

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.

Show details on source website


{
  "affected": [],
  "aliases": [
    "CVE-2022-50217"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-06-18T11:15:52Z",
    "severity": null
  },
  "details": "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 -\u003e 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.",
  "id": "GHSA-f5r8-w4hp-7v3r",
  "modified": "2025-06-18T12:30:56Z",
  "published": "2025-06-18T12:30:56Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-50217"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/035ff33cf4db101250fb980a3941bf078f37a544"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4bd9d5d20f344d015422969302d12653c903c271"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/5ccb0420b7c9334ab8122037847101931b899301"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…