CVE-2026-53388
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
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 2.6.35, < 5.15.211 |
| Linux | Linux Kernel | >= 5.16, < 6.1.177 |
| Linux | Linux Kernel | >= 6.2, < 6.6.144 |
| Linux | Linux Kernel | >= 6.7, < 6.12.95 |
| Linux | Linux Kernel | >= 6.13, < 6.18.37 |
| Linux | Linux Kernel | >= 6.19, < 7.0.14 |
| Linux | Linux Kernel | >= 7.1, < 7.1.2 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53388?
How severe is CVE-2026-53388?
How do I fix CVE-2026-53388?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53382In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53383In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53384In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53385In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53386In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53387In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53389In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5339A vulnerability was detected in Tenda G103 1.0.0.5. The impa…8.8
- CVE-2026-53390In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-53391In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53392In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53393In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53388?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
