CVE-2026-53388 (CVSS 7.8)

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

Is your site exposed to CVE-2026-53388?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

7.8

HIGH

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

EPSS — Exploit Prediction

0.0013

Probability of exploitation

0.03%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

References

Other 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 https://git.kernel.org/stable/c/a078484921052d0badd827fcc2770b5cfc1d4120 https://git.kernel.org/stable/c/af2892249d982a1c036ca456cc135374e68b6677 https://git.kernel.org/stable/c/e28db6ac4792d065ab32565fd9f0a2361c3d4666

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(). It has a CVSS v3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-53388? +

CVE-2026-53388 has a CVSS v3.1 score of 7.8 out of 10, rated HIGH. This is a high-severity vulnerability that should be prioritized for patching. The EPSS score is 0.0013, placing it in the 0th percentile for exploitation probability.

How do I check if I'm vulnerable to CVE-2026-53388? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

CVE-2026-53388