Answer in brief
CVE-2024-26704 records a Unknown severity vulnerability in ext4: fix double-free of blocks due to wrong extents moved_len. 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-26704 records a Unknown severity vulnerability in ext4: fix double-free of blocks due to wrong extents moved_len. 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 | 3.18 | Not reported |
| Linux/Linuxgeneric | >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <b4fbb89d722cbb16beaaea234b7230faaaf68c71 || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <afbcad9ae7d6d11608399188f03a837451b6b3a1 || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <d033a555d9a1cf53dbf3301af7199cc4a4c8f537 || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <afba9d11320dad5ce222ac8964caf64b7b4bedb1 || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <185eab30486ba3e7bf8b9c2e049c79a06ffd2bc1 || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <2883940b19c38d5884c8626483811acf4d7e148f || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <559ddacb90da1d8786dd8ec4fd76bbfa404eaef6 || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <55583e899a5357308274601364741a83e78d6ac4 | b4fbb89d722cbb16beaaea234b7230faaaf68c71, afbcad9ae7d6d11608399188f03a837451b6b3a1, d033a555d9a1cf53dbf3301af7199cc4a4c8f537, afba9d11320dad5ce222ac8964caf64b7b4bedb1, 185eab30486ba3e7bf8b9c2e049c79a06ffd2bc1, 2883940b19c38d5884c8626483811acf4d7e148f, 559ddacb90da1d8786dd8ec4fd76bbfa404eaef6, 55583e899a5357308274601364741a83e78d6ac4 |
Published upstream
Apr 3, 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: fix double-free of blocks due to wrong extents moved_len In ext4_move_extents(), moved_len is only updated when all moves are successfully executed, and only discards orig_inode and donor_inode preallocations when moved_len is not zero. When the loop fails to exit after successfully moving some extents, moved_len is not updated and remains at 0, so it does not discard the preallocations. If the moved extents overlap with the preallocated extents, the overlapped extents are freed twice in ext4_mb_release_inode_pa() and ext4_process_freed_data() (as described in commit 94d7c16cbbbd ("ext4: Fix double-free of blocks with EXT4_IOC_MOVE_EXT")), and bb_free is incremented twice. Hence when trim is executed, a zero-division bug is triggered in mb_update_avg_fragment_size() because bb_free is not zero and bb_fragments is zero. Therefore, update move_len after each extent move to avoid the issue.
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 | 3.18 | Not reported |
| Linux/Linuxgeneric | >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <b4fbb89d722cbb16beaaea234b7230faaaf68c71 || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <afbcad9ae7d6d11608399188f03a837451b6b3a1 || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <d033a555d9a1cf53dbf3301af7199cc4a4c8f537 || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <afba9d11320dad5ce222ac8964caf64b7b4bedb1 || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <185eab30486ba3e7bf8b9c2e049c79a06ffd2bc1 || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <2883940b19c38d5884c8626483811acf4d7e148f || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <559ddacb90da1d8786dd8ec4fd76bbfa404eaef6 || >=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <55583e899a5357308274601364741a83e78d6ac4 | b4fbb89d722cbb16beaaea234b7230faaaf68c71, afbcad9ae7d6d11608399188f03a837451b6b3a1, d033a555d9a1cf53dbf3301af7199cc4a4c8f537, afba9d11320dad5ce222ac8964caf64b7b4bedb1, 185eab30486ba3e7bf8b9c2e049c79a06ffd2bc1, 2883940b19c38d5884c8626483811acf4d7e148f, 559ddacb90da1d8786dd8ec4fd76bbfa404eaef6, 55583e899a5357308274601364741a83e78d6ac4 |
Published upstream
Apr 3, 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: fix double-free of blocks due to wrong extents moved_len In ext4_move_extents(), moved_len is only updated when all moves are successfully executed, and only discards orig_inode and donor_inode preallocations when moved_len is not zero. When the loop fails to exit after successfully moving some extents, moved_len is not updated and remains at 0, so it does not discard the preallocations. If the moved extents overlap with the preallocated extents, the overlapped extents are freed twice in ext4_mb_release_inode_pa() and ext4_process_freed_data() (as described in commit 94d7c16cbbbd ("ext4: Fix double-free of blocks with EXT4_IOC_MOVE_EXT")), and bb_free is incremented twice. Hence when trim is executed, a zero-division bug is triggered in mb_update_avg_fragment_size() because bb_free is not zero and bb_fragments is zero. Therefore, update move_len after each extent move to avoid the issue.
Quoted source text, attributed separately from HOL analysis.