Answer in brief
CVE-2021-47004 records a High severity (CVSS 7.1) vulnerability in f2fs: fix to avoid touching checkpointed data in get_victim(). 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.
CVSS is 7.1. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4354994f097d068a894aa1a0860da54571df3582 <105155a8146ddb54c119d8318964eef3859d109d || >=4354994f097d068a894aa1a0860da54571df3582 <1e116f87825f01a6380286472196882746b16f63 || >=4354994f097d068a894aa1a0860da54571df3582 <211372b2571520e394b56b431a0705586013b3ff || >=4354994f097d068a894aa1a0860da54571df3582 <61461fc921b756ae16e64243f72af2bfc2e620db | 105155a8146ddb54c119d8318964eef3859d109d, 1e116f87825f01a6380286472196882746b16f63, 211372b2571520e394b56b431a0705586013b3ff, 61461fc921b756ae16e64243f72af2bfc2e620db |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Feb 28, 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 4, 2026
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid touching checkpointed data in get_victim() In CP disabling mode, there are two issues when using LFS or SSR | AT_SSR mode to select victim: 1. LFS is set to find source section during GC, the victim should have no checkpointed data, since after GC, section could not be set free for reuse. Previously, we only check valid chpt blocks in current segment rather than section, fix it. 2. SSR | AT_SSR are set to find target segment for writes which can be fully filled by checkpointed and newly written blocks, we should never select such segment, otherwise it can cause panic or data corruption during allocation, potential case is described as below: a) target segment has 'n' (n < 512) ckpt valid blocks b) GC migrates 'n' valid blocks to other segment (segment is still in dirty list) c) GC migrates '512 - n' blocks to target segment (segment has 'n' cp_vblocks and '512 - n' vblocks) d) If GC selects target segment via {AT,}SSR allocator, however there is no free space in targe segment.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2021-47004 records a High severity (CVSS 7.1) vulnerability in f2fs: fix to avoid touching checkpointed data in get_victim(). 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.
CVSS is 7.1. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4354994f097d068a894aa1a0860da54571df3582 <105155a8146ddb54c119d8318964eef3859d109d || >=4354994f097d068a894aa1a0860da54571df3582 <1e116f87825f01a6380286472196882746b16f63 || >=4354994f097d068a894aa1a0860da54571df3582 <211372b2571520e394b56b431a0705586013b3ff || >=4354994f097d068a894aa1a0860da54571df3582 <61461fc921b756ae16e64243f72af2bfc2e620db | 105155a8146ddb54c119d8318964eef3859d109d, 1e116f87825f01a6380286472196882746b16f63, 211372b2571520e394b56b431a0705586013b3ff, 61461fc921b756ae16e64243f72af2bfc2e620db |
| Linux/Linuxgeneric | 4.20 | Not reported |
Published upstream
Feb 28, 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 4, 2026
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid touching checkpointed data in get_victim() In CP disabling mode, there are two issues when using LFS or SSR | AT_SSR mode to select victim: 1. LFS is set to find source section during GC, the victim should have no checkpointed data, since after GC, section could not be set free for reuse. Previously, we only check valid chpt blocks in current segment rather than section, fix it. 2. SSR | AT_SSR are set to find target segment for writes which can be fully filled by checkpointed and newly written blocks, we should never select such segment, otherwise it can cause panic or data corruption during allocation, potential case is described as below: a) target segment has 'n' (n < 512) ckpt valid blocks b) GC migrates 'n' valid blocks to other segment (segment is still in dirty list) c) GC migrates '512 - n' blocks to target segment (segment has 'n' cp_vblocks and '512 - n' vblocks) d) If GC selects target segment via {AT,}SSR allocator, however there is no free space in targe segment.
Quoted source text, attributed separately from HOL analysis.