Linux Kernel up to 6.12.22/6.13.10/6.14.1 exfat block_read_full_folio race condition

Summaryinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 6.12.22/6.13.10/6.14.1. This affects the function block_read_full_folio of the component exfat. The manipulation leads to race condition. This vulnerability is uniquely identified as CVE-2025-22036. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.22/6.13.10/6.14.1 and classified as problematic. This issue affects the function block_read_full_folio of the component exfat. The manipulation with an unknown input leads to a race condition vulnerability. Using CWE to declare the problem leads to CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. The impact remains unknown. The summary by CVE is:

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. mpage_read_folio > 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 > ... ... ... ... > . . another_function > 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.

It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2025-22036 since 12/29/2024. The exploitation is known to be difficult. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 237088 (SUSE SLED15 / SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2025:01614-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.12.23, 6.13.11, 6.14.2 or 6.15-rc1 eliminates this vulnerability. Applying the patch 49b0a6ab8e528a0c1c50e37cef9b9c7c121365f2/f7447286363dc1e410bf30b87d75168f3519f9cc/f807a6bf2005740fa26b4f59c4a003dc966b9afd/1bb7ff4204b6d4927e982cd256286c09ed4fd8ca is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (237088) and CERT Bund (WID-SEC-2025-0844). Be aware that VulDB is the high quality source for vulnerability data.

Affected

• Google Container-Optimized OS
• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• Oracle Linux
• SUSE openSUSE
• RESF Rocky Linux
• Open Source Linux Kernel
• Dell Avamar
• SolarWinds Security Event Manager
• Dell NetWorker
• Dell Secure Connect Gateway
• IBM QRadar SIEM

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.12.0
• 6.12.1
• 6.12.2
• 6.12.3
• 6.12.4
• 6.12.5
• 6.12.6
• 6.12.7
• 6.12.8
• 6.12.9
• 6.12.10
• 6.12.11
• 6.12.12
• 6.12.13
• 6.12.14
• 6.12.15
• 6.12.16
• 6.12.17
• 6.12.18
• 6.12.19
• 6.12.20
• 6.12.21
• 6.12.22
• 6.13.0
• 6.13.1
• 6.13.2
• 6.13.3
• 6.13.4
• 6.13.5
• 6.13.6
• 6.13.7
• 6.13.8
• 6.13.9
• 6.13.10
• 6.14.0
• 6.14.1

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion