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().
- Published Jul 19, 2026
- CVSS 7.8 high
- 0.1% chance of exploitation in the next 30 days (EPSS)
- A fix is available
Affected software
In the news
- Multiple vulnerabilities in the Ubuntu Linux kernel CERT-FR ·
- Multiple vulnerabilities in the SUSE Linux kernel CERT-FR ·
- Multiple vulnerabilities in the SUSE Linux kernel CERT-FR ·
- Multiple vulnerabilities in the Ubuntu Linux kernel CERT-FR ·
- Multiple vulnerabilities in the Ubuntu Linux kernel CERT-FR ·
- Multiple vulnerabilities in the SUSE Linux kernel CERT-FR ·