CVE-2025-22036exfat: fix random stack corruption after get_block
- 7.8HighCVSS base score
- 0.20%Exploitation in 30 daysEPSS · top 90% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 4 months later
· 4 months later
Published
- 16 months later
· 16 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CISA-ADPADP (enrichment) | 3.1 | High7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.20% · top 90% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 11a347fb6cef62ce47e84b97c45f2b2497c7593b – < 49b0a6ab8e528a0c1c50e37cef9b9c7c121365f2
- affected 11a347fb6cef62ce47e84b97c45f2b2497c7593b – < f7447286363dc1e410bf30b87d75168f3519f9cc
- affected 11a347fb6cef62ce47e84b97c45f2b2497c7593b – < f807a6bf2005740fa26b4f59c4a003dc966b9afd
- affected 11a347fb6cef62ce47e84b97c45f2b2497c7593b – < 1bb7ff4204b6d4927e982cd256286c09ed4fd8ca
- affected 6.8
- unaffected < 6.8
- unaffected 6.12.23 – ≤ 6.12.*
- unaffected 6.13.11 – ≤ 6.13.*
- unaffected 6.14.2 – ≤ 6.14.*
- unaffected 6.15 – ≤ *
References
References4
- https://git.kernel.org/stable/c/49b0a6ab8e528a0c1c50e37cef9b9c7c121365f2 (opens in a new tab)
- https://git.kernel.org/stable/c/f7447286363dc1e410bf30b87d75168f3519f9cc (opens in a new tab)
- https://git.kernel.org/stable/c/f807a6bf2005740fa26b4f59c4a003dc966b9afd (opens in a new tab)
- https://git.kernel.org/stable/c/1bb7ff4204b6d4927e982cd256286c09ed4fd8ca (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-11260 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-22036)Record last updated .