CVE-2021-47004

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

State
Published
Severity
7.1 High
Published
Feb 28, 2024
Updated
Aug 5, 2026
Reserved
Feb 27, 2024

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.1 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 4354994f097d068a894aa1a0860da54571df3582 to before 105155a8146ddb54c119d8318964eef3859d109dAffected
  • 4354994f097d068a894aa1a0860da54571df3582 to before 1e116f87825f01a6380286472196882746b16f63Affected
  • 4354994f097d068a894aa1a0860da54571df3582 to before 211372b2571520e394b56b431a0705586013b3ffAffected
  • 4354994f097d068a894aa1a0860da54571df3582 to before 61461fc921b756ae16e64243f72af2bfc2e620dbAffected
LinuxLinux
  • 4.20Affected
  • before 4.20Not affected
  • 5.10.38 through 5.10.*Not affected
  • 5.11.22 through 5.11.*Not affected
  • 5.12.5 through 5.12.*Not affected
  • 5.13 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.