CVE-2025-22036 Details
Description
In the Linux kernel, the following vulnerability has been resolved: exfat: fix random stack corruption after get_block When get_block is called with a buffer_head allocated on the stack, such as do_mpage_readpage, stack corruption due to buffer_head UAF may occur in the following race condition situation. <CPU 0> <CPU 1> mpage_read_folio <<bh on stack>> do_mpage_readpage exfat_get_block bh_read __bh_read get_bh(bh) submit_bh wait_on_buffer ... end_buffer_read_sync __end_buffer_read_notouch unlock_buffer <<keep going>> ... ... ... ... <<bh is not valid out of mpage_read_folio>> . . another_function <<variable A on stack>> put_bh(bh) atomic_dec(bh->b_count) * stack corruption here * This patch returns -EAGAIN if a folio does not have buffers when bh_read needs to be called. By doing this, the caller can fallback to functions like block_read_full_folio(), create a buffer_head in the folio, and then call get_block again. Let's do not call bh_read() with on-stack buffer_head.
A vulnerability in the Linux kernel's exFAT file system implementation can lead to random stack corruption. This issue arises when the 'get_block' function is called with a 'buffer_head' that is allocated on the stack, such as during 'do_mpage_readpage' operations. The vulnerability is caused by a use-after-free condition, where the 'buffer_head' becomes invalid after being processed, yet can still be accessed, leading to stack corruption. The issue occurs in a race condition scenario, where one CPU is reading data while another CPU is simultaneously freeing the 'buffer_head', created a conflict that can be exploited.
The vulnerability has been addressed in the Linux kernel by modifying the exFAT implementation. The patch ensures that 'get_block' is not called with 'buffer_head' objects allocated on the stack, preventing the stack corruption issue. Users should upgrade to the patched version of the Linux kernel.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Oct 1, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1bb7ff4204b6d4927e982cd256286c09ed4fd8ca | kernel.org | Patch |
| https://git.kernel.org/stable/c/49b0a6ab8e528a0c1c50e37cef9b9c7c121365f2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/f7447286363dc1e410bf30b87d75168f3519f9cc | kernel.org | Patch |
| https://git.kernel.org/stable/c/f807a6bf2005740fa26b4f59c4a003dc966b9afd | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | [email protected] |
| CWE-416 | Use After Free | [email protected] |
| CWE-416 | Use After Free | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.8, < 6.12.23 >= 6.13, < 6.13.11 >= 6.14, < 6.14.2 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Oct 1, 2025 | CVE Modified | CISA-ADP |
| Apr 29, 2025 | Initial Analysis | [email protected] |
| Apr 16, 2025 | New CVE Received | kernel.org |