CVE-2026-53388
published 2026-07-19CVE-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…
PriorityP341high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.13%
3.2th percentile
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().
Affected
17 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| linux | linux | — | — |
| linux | linux | >= ce534fb052928ce556639d7ecf01cbf4e01321e1 < 7c18691e0cfda29672f79bafde8abdb7710674f6 | 7c18691e0cfda29672f79bafde8abdb7710674f6 |
| linux | linux | >= ce534fb052928ce556639d7ecf01cbf4e01321e1 < 5927b43a4f8d89e86930f524bf63e9c7e66f61b4 | 5927b43a4f8d89e86930f524bf63e9c7e66f61b4 |
| linux | linux | >= ce534fb052928ce556639d7ecf01cbf4e01321e1 < 030fe3e9d8abdee303dd7e9e42f45082d382a407 | 030fe3e9d8abdee303dd7e9e42f45082d382a407 |
| linux | linux | >= ce534fb052928ce556639d7ecf01cbf4e01321e1 < 46473ddccdc5065033e397d6e62c280dbcd3d9c2 | 46473ddccdc5065033e397d6e62c280dbcd3d9c2 |
| linux | linux | >= ce534fb052928ce556639d7ecf01cbf4e01321e1 < af2892249d982a1c036ca456cc135374e68b6677 | af2892249d982a1c036ca456cc135374e68b6677 |
| linux | linux | >= ce534fb052928ce556639d7ecf01cbf4e01321e1 < 0223f452532d9cd8a5e87c45de828fd93c99bd25 | 0223f452532d9cd8a5e87c45de828fd93c99bd25 |
| linux | linux | >= ce534fb052928ce556639d7ecf01cbf4e01321e1 < e28db6ac4792d065ab32565fd9f0a2361c3d4666 | e28db6ac4792d065ab32565fd9f0a2361c3d4666 |
| linux | linux | >= ce534fb052928ce556639d7ecf01cbf4e01321e1 < a078484921052d0badd827fcc2770b5cfc1d4120 | a078484921052d0badd827fcc2770b5cfc1d4120 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 2.6.35 < 5.15.211 | 5.15.211 |
| linux | linux_kernel | >= 5.16 < 6.1.177 | 6.1.177 |
| linux | linux_kernel | >= 6.13 < 6.18.37 | 6.18.37 |
| linux | linux_kernel | >= 6.19 < 7.0.14 | 7.0.14 |
| linux | linux_kernel | >= 6.2 < 6.6.144 | 6.6.144 |
| linux | linux_kernel | >= 6.7 < 6.12.95 | 6.12.95 |
| linux | linux_kernel | >= 7.1 < 7.1.2 | 7.1.2 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
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
ghsa_unreviewed·2026-07-19
CVE-2026-53388 [HIGH] 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
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
Red Hat
kernel: fuse: re-lock request before replacing page cache folio
vendor_redhat·2026-07-19·CVSS 7.8
CVE-2026-53388 [HIGH] CWE-825 kernel: fuse: re-lock request before replacing page cache folio
kernel: fuse: re-lock request before replacing page cache folio
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->
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0223f452532d9cd8a5e87c45de828fd93c99bd25https://git.kernel.org/stable/c/030fe3e9d8abdee303dd7e9e42f45082d382a407https://git.kernel.org/stable/c/46473ddccdc5065033e397d6e62c280dbcd3d9c2https://git.kernel.org/stable/c/5927b43a4f8d89e86930f524bf63e9c7e66f61b4https://git.kernel.org/stable/c/7c18691e0cfda29672f79bafde8abdb7710674f6https://git.kernel.org/stable/c/a078484921052d0badd827fcc2770b5cfc1d4120https://git.kernel.org/stable/c/af2892249d982a1c036ca456cc135374e68b6677https://git.kernel.org/stable/c/e28db6ac4792d065ab32565fd9f0a2361c3d4666
2026-07-19
Published