CVE-2026-53388

HIGHCVSS 7.8/10EPSS 0.13%

Last modified

CVE-2026-53388 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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().. EPSS estimates a 0.13% chance of exploitation in the next 30 days.

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

Metrics

CVSS 3.1
7.8/10

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

EPSS Probability
0.13%

3.2th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= ce534fb052928ce556639d7ecf01cbf4e01321e1, < 7c18691e0cfda29672f79bafde8abdb7710674f6; >= ce534fb052928ce556639d7ecf01cbf4e01321e1, < 5927b43a4f8d89e86930f524bf63e9c7e66f61b4; >= ce534fb052928ce556639d7ecf01cbf4e01321e1, < 030fe3e9d8abdee303dd7e9e42f45082d382a407; >= ce534fb052928ce556639d7ecf01cbf4e01321e1, < 46473ddccdc5065033e397d6e62c280dbcd3d9c2; >= ce534fb052928ce556639d7ecf01cbf4e01321e1, < af2892249d982a1c036ca456cc135374e68b6677; >= ce534fb052928ce556639d7ecf01cbf4e01321e1, < 0223f452532d9cd8a5e87c45de828fd93c99bd25; >= ce534fb052928ce556639d7ecf01cbf4e01321e1, < e28db6ac4792d065ab32565fd9f0a2361c3d4666; >= ce534fb052928ce556639d7ecf01cbf4e01321e1, < a078484921052d0badd827fcc2770b5cfc1d4120
LinuxLinux2.6.35

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is 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().
How severe is CVE-2026-53388?
CVE-2026-53388 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.13% probability of exploitation in the next 30 days.
How do I fix CVE-2026-53388?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-53388?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST