In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix panic during f2fsresizefs()
f2fsresizefs() 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: allocatesegmentbydefault+0x92/0xf0 [f2fs] f2fsallocatedatablock+0x44b/0x7e0 [f2fs] dowritepage+0x5a/0x110 [f2fs] f2fsoutplacewritedata+0x55/0x100 [f2fs] f2fsdowritedatapage+0x392/0x850 [f2fs] movedatapage+0x233/0x320 [f2fs] dogarbagecollect+0x14d9/0x1660 [f2fs] freesegmentrange+0x1f7/0x310 [f2fs] f2fsresize_fs+0x118/0x330 [f2fs] __f2fs_ioctl+0x487/0x3680 [f2fs] __x64sysioctl+0x8e/0xd0 dosyscall64+0x33/0x80 entrySYSCALL64afterhwframe+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 freesegmentrange().
[
{
"events": [
{
"introduced": "5.8"
},
{
"fixed": "5.10.38"
}
]
},
{
"events": [
{
"introduced": "5.11"
},
{
"fixed": "5.11.22"
}
]
},
{
"events": [
{
"introduced": "5.12"
},
{
"fixed": "5.12.5"
}
]
}
]
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2021-47007.json"