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().
References
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-07-19 12:16
Updated : 2026-08-17 05:17
NVD link : CVE-2026-53388
Mitre link : CVE-2026-53388
CVE.ORG link : CVE-2026-53388
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-416
Use After Free
