CVE-2021-47004

f2fs: fix to avoid touching checkpointed data in get_victim()

HIGH
7.1
CVSS Score
Published: February 28, 2024 at 08:13 AM UTC
Updated: August 5, 2026 at 09:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.20 ≤ v < 5.10.384.20 ≤ v < 5.11.224.20 ≤ v < 5.12.54.20 ≤ v < 5.135.11 ≤ v < 5.11.225.12 ≤ v < 5.12.54.204354994f097d068a894aa1a0860da54571df3582
Vendor states this is fixed in 105155a8146ddb54c119d8318964eef3859d109d (fixed)
Vendor states this is fixed in 1e116f87825f01a6380286472196882746b16f63 (fixed)
Vendor states this is fixed in 211372b2571520e394b56b431a0705586013b3ff (fixed)
Vendor states this is fixed in 61461fc921b756ae16e64243f72af2bfc2e620db (fixed)
Vendor states this is fixed in 4.20 (unaffected)
Vendor states this is fixed in 5.10.38 (unaffected)
Vendor states this is fixed in 5.11.22 (unaffected)
Vendor states this is fixed in 5.12.5 (unaffected)
Vendor states this is fixed in 5.13 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/105155a8146ddb54c119d8318964eef3859d109d
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/1e116f87825f01a6380286472196882746b16f63
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/211372b2571520e394b56b431a0705586013b3ff
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/61461fc921b756ae16e64243f72af2bfc2e620db

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.1HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card