CVE-2025-21896
Last modified
CVE-2025-21896 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: fuse: revert back to __readahead_folio() for readahead In commit 3eab9d7bc2f4 ("fuse: convert readahead to use folios"), the logic was converted to using the new folio readahead code, which drops the reference on the folio once it is locked, using an inferred reference on the folio. Previously we held a reference on the folio for the entire duration of the readpages call. This is fine, however for the case for splice pipe responses where we will remove the old folio and splice in the new folio (see fuse_try_move_page()), we assume that there is a reference held on the folio for ap->folios, which is no longer the case. To fix this, revert back to __readahead_folio() which allows us to hold the reference on the folio for the duration of readpages until either we drop the reference ourselves in fuse_readpages_end() or the reference is dropped after it's replaced in the page cache in the splice case. This will fix the UAF bug that was reported.. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: fuse: revert back to __readahead_folio() for readahead In commit 3eab9d7bc2f4 ("fuse: convert readahead to use folios"), the logic was converted to using the new folio readahead code, which drops the reference on the folio once it is locked, using an inferred reference on the folio. Previously we held a reference on the folio for the entire duration of the readpages call. This is fine, however for the case for splice pipe responses where we will remove the old folio and splice in the new folio (see fuse_try_move_page()), we assume that there is a reference held on the folio for ap->folios, which is no longer the case. To fix this, revert back to __readahead_folio() which allows us to hold the reference on the folio for the duration of readpages until either we drop the reference ourselves in fuse_readpages_end() or the reference is dropped after it's replaced in the page cache in the splice case. This will fix the UAF bug that was reported.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.13, < 6.13.6 | — |
| Linux | Linux Kernel | 6.14 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-21896?
How severe is CVE-2025-21896?
How do I fix CVE-2025-21896?
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 2025
- CVE-2025-21890In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21891In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21892In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-21893In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-21894In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21895In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-21897In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21898In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21899In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-2190The mobile application (com.transsnet.store) has a man-in-th…8.1
- CVE-2025-21900In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21901In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-21896?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
