CVE-2026-53388

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().

CVSS 3.1

7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

0.1% chance of exploitation in the next 30 days; higher than 2% of CVEs (scores of 2026-10-25)

CWE

CWE-416

Published

2026-07-19

Modified

2026-10-19

Record from

the NVD, synced 2026-10-21

Affected

• linux:linux_kernel

References

• https://git.kernel.org/stable/c/0223f452532d9cd8a5e87c45de828fd93c99bd25
• https://git.kernel.org/stable/c/030fe3e9d8abdee303dd7e9e42f45082d382a407
• https://git.kernel.org/stable/c/46473ddccdc5065033e397d6e62c280dbcd3d9c2
• https://git.kernel.org/stable/c/5927b43a4f8d89e86930f524bf63e9c7e66f61b4
• https://git.kernel.org/stable/c/7c18691e0cfda29672f79bafde8abdb7710674f6

Check your stackJSON