# CVE-2025-22036: exfat: fix random stack corruption after get_block > A race condition in the Linux kernel exFAT driver causes stack corruption via use-after-free, potentially allowing local attackers to execute code or escalate privileges. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Apr 2025 - **Updated:** 5 Aug 2026 - **Also known as:** ALSA-2025:10854, BELL-CVE-2025-22036, DEBIAN-CVE-2025-22036, GHSA-4hwj-3ppp-cx8v, RHSA-2025:10854, RLSA-2025:10854, ROOT-OS-UBUNTU-2404-CVE-2025-22036, UBUNTU-CVE-2025-22036 ## What is CVE-2025-22036? CVE-2025-22036 is a high-severity use after free vulnerability in Linux kernel, published on 16 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official 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. 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. Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization), CWE-416 (Use After Free) ## Which versions are affected by CVE-2025-22036? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel-abi-stablelists` | AlmaLinux:10 | All versions | 6.12.0-55.21.1.el10_0 | | `kernel-doc` | AlmaLinux:10 | All versions | 6.12.0-55.21.1.el10_0 | | `kernel` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-core` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-debug` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-debug-core` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-debug-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-debug-devel` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-debug-devel-matched` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-debug-modules` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-debug-modules-core` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-debug-modules-extra` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-devel` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-devel-matched` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-modules` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-modules-core` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-64k-modules-extra` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-abi-stablelists` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-core` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debug` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debug-core` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debug-devel` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debug-devel-matched` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debug-modules` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debug-modules-core` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debug-modules-extra` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debug-uki-virt` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debuginfo-common-aarch64` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debuginfo-common-ppc64le` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debuginfo-common-s390x` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-devel` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-devel-matched` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-doc` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-modules` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | | `kernel-modules-core` | Red Hat:enterprise_linux:10.0 | All versions | 0:6.12.0-55.21.1.el10_0 | Products: Linux kernel. ## How do I fix CVE-2025-22036? Apply the vendor's patch. ## Is CVE-2025-22036 being exploited? There is no known exploitation of CVE-2025-22036 in the wild and no public exploit code. ## Other vulnerabilities in Linux kernel - [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild) - [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild) - [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild) - [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild) - [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-22036 and fix it if it is affected. What it is: CVE-2025-22036 is a high-severity use after free vulnerability in Linux kernel, published on 16 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-22036 in the wild and no public exploit code. Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-22036/ (Markdown: https://insights.sbomify.com/CVE-2025-22036/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22036 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22036 - OSV: https://osv.dev/vulnerability/CVE-2025-22036 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-22036/ Summaries are generated and may contain mistakes; the official description above is the record.