Vulnerabilities · 2025 · Linux
CVE-2025-22036
Linux Kernel vulnerability
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.
Affected products
Linux Kernel. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Linux Kernel runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/1bb7ff4204b6d4927e982cd256286c09ed4fd8ca · Patch
- git.kernel.org/stable/c/49b0a6ab8e528a0c1c50e37cef9b9c7c121365f2 · Patch
- git.kernel.org/stable/c/f7447286363dc1e410bf30b87d75168f3519f9cc · Patch
- git.kernel.org/stable/c/f807a6bf2005740fa26b4f59c4a003dc966b9afd · Patch
- nvd.nist.gov/vuln/detail/CVE-2025-22036
- cve.org/CVERecord?id=CVE-2025-22036
More vulnerabilities in Linux products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.