CVE-2021-47007
f2fs: fix panic during f2fs_resize_fs()
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix panic during f2fs_resize_fs() f2fs_resize_fs() hangs in below callstack with testcase: - mkfs 16GB image & mount image - dd 8GB fileA - dd 8GB fileB - sync - rm fileA - sync - resize filesystem to 8GB kernel BUG at segment.c:2484! Call Trace: allocate_segment_by_default+0x92/0xf0 [f2fs] f2fs_allocate_data_block+0x44b/0x7e0 [f2fs] do_write_page+0x5a/0x110 [f2fs] f2fs_outplace_write_data+0x55/0x100 [f2fs] f2fs_do_write_data_page+0x392/0x850 [f2fs] move_data_page+0x233/0x320 [f2fs] do_garbage_collect+0x14d9/0x1660 [f2fs] free_segment_range+0x1f7/0x310 [f2fs] f2fs_resize_fs+0x118/0x330 [f2fs] __f2fs_ioctl+0x487/0x3680 [f2fs] __x64_sys_ioctl+0x8e/0xd0 do_syscall_64+0x33/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xa9 The root cause is we forgot to check that whether we have enough space in resized filesystem to store all valid blocks in before-resizing filesystem, then allocator will run out-of-space during block migration in free_segment_range().
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (7 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Weakness
Affected products
- affected b4b10061ef98c583bcf82a4200703fbaa98c18dc – < 1c20a4896409f5ca1c770e1880c33d0a28a8b10f
- affected b4b10061ef98c583bcf82a4200703fbaa98c18dc – < 860afd680d9cc1dabd61cda3cd246f60aa1eb705
- affected b4b10061ef98c583bcf82a4200703fbaa98c18dc – < 822054e5026c43b1dd60cf387dd999e95ee2ecc2
- affected b4b10061ef98c583bcf82a4200703fbaa98c18dc – < 3ab0598e6d860ef49d029943ba80f627c15c15d6
- affected 5.8
- unaffected < 5.8
- unaffected 5.10.38 – ≤ 5.10.*
- unaffected 5.11.22 – ≤ 5.11.*
- unaffected 5.12.5 – ≤ 5.12.*
- unaffected 5.13 – ≤ *
References (4)
- https://git.kernel.org/stable/c/1c20a4896409f5ca1c770e1880c33d0a28a8b10f (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/860afd680d9cc1dabd61cda3cd246f60aa1eb705 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/822054e5026c43b1dd60cf387dd999e95ee2ecc2 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/3ab0598e6d860ef49d029943ba80f627c15c15d6 (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2021-47007)Record last updated .