Answer in brief
CVE-2025-22036 records a Unknown severity vulnerability in exfat: fix random stack corruption after get_block. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=11a347fb6cef62ce47e84b97c45f2b2497c7593b <49b0a6ab8e528a0c1c50e37cef9b9c7c121365f2 || >=11a347fb6cef62ce47e84b97c45f2b2497c7593b <f7447286363dc1e410bf30b87d75168f3519f9cc || >=11a347fb6cef62ce47e84b97c45f2b2497c7593b <f807a6bf2005740fa26b4f59c4a003dc966b9afd || >=11a347fb6cef62ce47e84b97c45f2b2497c7593b <1bb7ff4204b6d4927e982cd256286c09ed4fd8ca | 49b0a6ab8e528a0c1c50e37cef9b9c7c121365f2, f7447286363dc1e410bf30b87d75168f3519f9cc, f807a6bf2005740fa26b4f59c4a003dc966b9afd, 1bb7ff4204b6d4927e982cd256286c09ed4fd8ca |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-22036 records a Unknown severity vulnerability in exfat: fix random stack corruption after get_block. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=11a347fb6cef62ce47e84b97c45f2b2497c7593b <49b0a6ab8e528a0c1c50e37cef9b9c7c121365f2 || >=11a347fb6cef62ce47e84b97c45f2b2497c7593b <f7447286363dc1e410bf30b87d75168f3519f9cc || >=11a347fb6cef62ce47e84b97c45f2b2497c7593b <f807a6bf2005740fa26b4f59c4a003dc966b9afd || >=11a347fb6cef62ce47e84b97c45f2b2497c7593b <1bb7ff4204b6d4927e982cd256286c09ed4fd8ca | 49b0a6ab8e528a0c1c50e37cef9b9c7c121365f2, f7447286363dc1e410bf30b87d75168f3519f9cc, f807a6bf2005740fa26b4f59c4a003dc966b9afd, 1bb7ff4204b6d4927e982cd256286c09ed4fd8ca |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.