ext4: avoid online resizing failures due to oversized flex bg
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.19.307, 5.4.269, 5.10.210, 5.15.149, 6.1.77, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid online resizing failures due to oversized flex bg When we online resize an ext4 filesystem with a oversized flexbg_size, mkfs.ext4 -F -G 67108864 $dev -b 4096 100M mount $dev $dir resize2fs $dev 16G the following WARN_ON is triggered: ================================================================== WARNING: CPU: 0 PID: 427 at mm/page_alloc.c:4402 __alloc_pages+0x411/0x550 Modules linked in: sg(E) CPU: 0 PID: 427 Comm: resize2fs Tainted: G E 6.6.0-rc5+ #314 RIP: 0010:__alloc_pages+0x411/0x550 Call Trace: <TASK> __kmalloc_large_node+0xa2/0x200 __kmalloc+0x16e/0x290 ext4_resize_fs+0x481/0xd80 __ext4_ioctl+0x1616/0x1d90 ext4_ioctl+0x12/0x20 __x64_sys_ioctl+0xf0/0x150 do_syscall_64+0x3b/0x90 ================================================================== This is because flexbg_size is too large and the size of the new_group_data array to be allocated exceeds MAX_ORDER. Currently, the minimum value of MAX_ORDER is 8, the minimum value of PAGE_SIZE is 4096, the corresponding maximum number of groups that can be allocated is: (PAGE_SIZE << MAX_ORDER) / sizeof(struct ext4_new_group_data) ≈ 21845 And the value that is down-aligned to the power of 2 is 16384. Therefore, this value is defined as MAX_RESIZE_BG, and the number of groups added each time does not exceed this value during resizing, and is added multiple times to complete the online resizing. The difference is that the metadata in a flex_bg may be more dispersed.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 28c7bac0091687e6116ebd6c179e154ae4053c90 · fixed in cd1f93ca97a9136989f3bd2bf90696732a2ed644; From 28c7bac0091687e6116ebd6c179e154ae4053c90 · fixed in b183fe8702e78bba3dcef8e7193cab6898abee07; From 28c7bac0091687e6116ebd6c179e154ae4053c90 · fixed in cfbbb3199e71b63fc26cee0ebff327c47128a1e8; From 28c7bac0091687e6116ebd6c179e154ae4053c90 · fixed in d76c8d7ffe163c6bf2f1ef680b0539c2b3902b90; From 28c7bac0091687e6116ebd6c179e154ae4053c90 · fixed in 6d2cbf517dcabc093159cf138ad5712c9c7fa954; From 28c7bac0091687e6116ebd6c179e154ae4053c90 · fixed in 8b1413dbfe49646eda2c00c0f1144ee9d3368e0c; From 28c7bac0091687e6116ebd6c179e154ae4053c90 · fixed in dc3e0f55bec4410f3d74352c4a7c79f518088ee2; From 28c7bac0091687e6116ebd6c179e154ae4053c90 · fixed in 5d1935ac02ca5aee364a449a35e2977ea84509b0
- Linux Linux
3.3
- KernelLinux
From 3.3.0 · fixed in 4.19.307; From 4.20.0 · fixed in 5.4.269; From 5.5.0 · fixed in 5.10.210; From 5.11.0 · fixed in 5.15.149; From 5.16.0 · fixed in 6.1.77; From 6.2.0 · fixed in 6.6.16; From 6.7.0 · fixed in 6.7.4
References 8
git.kernel.org
- stable/c/cd1f93ca97a9136989f3bd2bf90696732a2ed644
- stable/c/b183fe8702e78bba3dcef8e7193cab6898abee07
- stable/c/cfbbb3199e71b63fc26cee0ebff327c47128a1e8
- stable/c/d76c8d7ffe163c6bf2f1ef680b0539c2b3902b90
- stable/c/6d2cbf517dcabc093159cf138ad5712c9c7fa954
- stable/c/8b1413dbfe49646eda2c00c0f1144ee9d3368e0c
- stable/c/dc3e0f55bec4410f3d74352c4a7c79f518088ee2
- stable/c/5d1935ac02ca5aee364a449a35e2977ea84509b0