Description
In the Linux kernel, the following vulnerability has been resolved:

fuse: re-lock request before replacing page cache folio

fuse_try_move_folio() unlocks the request on entry but does not
re-lock it on the success path. This means fuse_chan_abort() can end the
request and free the fuse_io_args (eg fuse_readpages_end()) while the
subsequent copy chain logic after fuse_try_move_folio() accesses the
fuse_io_args, leading to use-after-free issues.

Fix this by calling lock_request() before replace_page_cache_folio().
This ensures the request is locked on the success path which will
prevent the fuse_io_args from being freed while the later copying logic
runs, and also ensures that the ap->folios[i]->mapping is never null
since ap->folios[i] will always point to the newfolio after
replace_page_cache_folio().
Published: 2026-07-19
Score: 7.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability occurs in the fuse subsystem of the Linux kernel when fuse_try_move_folio() unlocks a request on entry but fails to re-lock it on the success path. This oversight can allow fuse_chan_abort() to end the request and free fuse_io_args while subsequent copy-chain logic still accesses them, resulting in a use‑after‑free condition. Based on the description, it is inferred that an attacker could exploit this race condition to corrupt kernel memory or execute arbitrary code with the privileges of the process generating the request. This issue is classified as CWE‑825, which corresponds to a use‑after‑free scenario involving dereferencing freed memory.

Affected Systems

All Linux kernel installations that include the fuse component are potentially affected, as the flaw exists in the core fuse source and applies to any variant of the kernel where fuse is compiled in. No specific kernel releases are identified in the advisory, so any version prior to the patch could be vulnerable.

Risk and Exploitability

The CVSS score of 7.8 denotes high severity, yet the EPSS score is below 1%, indicating a very low probability of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog, suggesting no known active exploitation. Based on the description, it is inferred that the attack vector is probably local, as the flaw involves interaction with fuse page-cache management. Remote exploitation would require prior compromise or privileged access. Systems that expose fuse filesystems to other users may increase risk.

Generated by OpenCVE AI on August 1, 2026 at 08:03 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to a Linux kernel version that includes the patch re‑locking the request before replacing the page cache folio.
  • If an immediate kernel upgrade is not possible, disable the fuse filesystem on critical hosts to reduce the attack surface.
  • Reboot the system after applying the updated kernel to ensure the patched code is loaded.

Generated by OpenCVE AI on August 1, 2026 at 08:03 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4700-1 linux-6.1 security update
History

Tue, 21 Jul 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-825
References
Metrics threat_severity

None

threat_severity

Moderate


Mon, 20 Jul 2026 14:45:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Sun, 19 Jul 2026 12:15:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before replacing page cache folio fuse_try_move_folio() unlocks the request on entry but does not re-lock it on the success path. This means fuse_chan_abort() can end the request and free the fuse_io_args (eg fuse_readpages_end()) while the subsequent copy chain logic after fuse_try_move_folio() accesses the fuse_io_args, leading to use-after-free issues. Fix this by calling lock_request() before replace_page_cache_folio(). This ensures the request is locked on the success path which will prevent the fuse_io_args from being freed while the later copying logic runs, and also ensures that the ap->folios[i]->mapping is never null since ap->folios[i] will always point to the newfolio after replace_page_cache_folio().
Title fuse: re-lock request before replacing page cache folio
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-05T12:35:27.831Z

Reserved: 2026-06-09T07:44:35.402Z

Link: CVE-2026-53388

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-07-19T00:00:00Z

Links: CVE-2026-53388 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-01T08:15:03Z

Weaknesses
  • CWE-825

    Expired Pointer Dereference