CVE-2026-53388
What it is
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().
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- Linux Kernel < 5.15.211
- Linux Kernel < 6.1.177
- Linux Kernel < 6.6.144
- Linux Kernel < 6.12.95
- Linux Kernel < 6.18.37
- Linux Kernel < 7.0.14
- Linux Kernel < 7.1.2
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-53388.md and follow it. Check whether this project is affected by CVE-2026-53388. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- 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
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