Answer in brief
CVE-2024-26601 records a Unknown severity vulnerability in ext4: regenerate buddy after block freeing failed if under fc replay. 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.
Answer in brief
CVE-2024-26601 records a Unknown severity vulnerability in ext4: regenerate buddy after block freeing failed if under fc replay. 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 | >=0983142c5f17a62055ec851372273c3bc77e4788 <94ebf71bddbcd4ab1ce43ae32c6cb66396d2d51a || >=6bd97bf273bdb4944904e57480f6545bca48ad77 <c1317822e2de80e78f137d3a2d99febab1b80326 || >=6bd97bf273bdb4944904e57480f6545bca48ad77 <78327acd4cdc4a1601af718b781eece577b6b7d4 || >=6bd97bf273bdb4944904e57480f6545bca48ad77 <ea42d6cffb0dd27a417f410b9d0011e9859328cb || >=6bd97bf273bdb4944904e57480f6545bca48ad77 <6b0d48647935e4b8c7b75d1eccb9043fcd4ee581 || >=6bd97bf273bdb4944904e57480f6545bca48ad77 <c9b528c35795b711331ed36dc3dbee90d5812d4e || >=5.10.181 <5.10.211 | 94ebf71bddbcd4ab1ce43ae32c6cb66396d2d51a, c1317822e2de80e78f137d3a2d99febab1b80326, 78327acd4cdc4a1601af718b781eece577b6b7d4, ea42d6cffb0dd27a417f410b9d0011e9859328cb, 6b0d48647935e4b8c7b75d1eccb9043fcd4ee581, c9b528c35795b711331ed36dc3dbee90d5812d4e, 5.10.211 |
| Linux/Linuxgeneric | 5.11 | Not reported |
Published upstream
Feb 24, 2024
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: ext4: regenerate buddy after block freeing failed if under fc replay This mostly reverts commit 6bd97bf273bd ("ext4: remove redundant mb_regenerate_buddy()") and reintroduces mb_regenerate_buddy(). Based on code in mb_free_blocks(), fast commit replay can end up marking as free blocks that are already marked as such. This causes corruption of the buddy bitmap so we need to regenerate it in that case.
Quoted source text, attributed separately from HOL analysis.
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 | >=0983142c5f17a62055ec851372273c3bc77e4788 <94ebf71bddbcd4ab1ce43ae32c6cb66396d2d51a || >=6bd97bf273bdb4944904e57480f6545bca48ad77 <c1317822e2de80e78f137d3a2d99febab1b80326 || >=6bd97bf273bdb4944904e57480f6545bca48ad77 <78327acd4cdc4a1601af718b781eece577b6b7d4 || >=6bd97bf273bdb4944904e57480f6545bca48ad77 <ea42d6cffb0dd27a417f410b9d0011e9859328cb || >=6bd97bf273bdb4944904e57480f6545bca48ad77 <6b0d48647935e4b8c7b75d1eccb9043fcd4ee581 || >=6bd97bf273bdb4944904e57480f6545bca48ad77 <c9b528c35795b711331ed36dc3dbee90d5812d4e || >=5.10.181 <5.10.211 | 94ebf71bddbcd4ab1ce43ae32c6cb66396d2d51a, c1317822e2de80e78f137d3a2d99febab1b80326, 78327acd4cdc4a1601af718b781eece577b6b7d4, ea42d6cffb0dd27a417f410b9d0011e9859328cb, 6b0d48647935e4b8c7b75d1eccb9043fcd4ee581, c9b528c35795b711331ed36dc3dbee90d5812d4e, 5.10.211 |
| Linux/Linuxgeneric | 5.11 | Not reported |
Published upstream
Feb 24, 2024
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: ext4: regenerate buddy after block freeing failed if under fc replay This mostly reverts commit 6bd97bf273bd ("ext4: remove redundant mb_regenerate_buddy()") and reintroduces mb_regenerate_buddy(). Based on code in mb_free_blocks(), fast commit replay can end up marking as free blocks that are already marked as such. This causes corruption of the buddy bitmap so we need to regenerate it in that case.
Quoted source text, attributed separately from HOL analysis.