CVE-2021-47256
published 2024-05-21CVE-2021-47256: In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: make sure wait for page writeback in memory_failure Our syzkaller…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.23%
14.3th percentile
In the Linux kernel, the following vulnerability has been resolved:
mm/memory-failure: make sure wait for page writeback in memory_failure
Our syzkaller trigger the "BUG_ON(!list_empty(&inode->i_wb_list))" in
clear_inode:
kernel BUG at fs/inode.c:519!
Internal error: Oops - BUG: 0 [#1] SMP
Modules linked in:
Process syz-executor.0 (pid: 249, stack limit = 0x00000000a12409d7)
CPU: 1 PID: 249 Comm: syz-executor.0 Not tainted 4.19.95
Hardware name: linux,dummy-virt (DT)
pstate: 80000005 (Nzcv daif -PAN -UAO)
pc : clear_inode+0x280/0x2a8
lr : clear_inode+0x280/0x2a8
Call trace:
clear_inode+0x280/0x2a8
ext4_clear_inode+0x38/0xe8
ext4_free_inode+0x130/0xc68
ext4_evict_inode+0xb20/0xcb8
evict+0x1a8/0x3c0
iput+0x344/0x460
do_unlinkat+0x260/0x410
__arm64_sys_unlinkat+0x6c/0xc0
el0_svc_common+0xdc/0x3b0
el0_svc_handler+0xf8/0x160
el0_svc+0x10/0x218
Kernel panic - not syncing: Fatal exception
A crash dump of this problem show that someone called __munlock_pagevec
to clear page LRU without lock_page: do_mmap -> mmap_region -> do_munmap
-> munlock_vma_pages_range -> __munlock_pagevec.
As a result memory_failure will call identify_page_state without
wait_on_page_writeback. And after truncate_error_page clear the mapping
of this page. end_page_writeback won't call sb_clear_inode_writeback to
clear inode->i_wb_list. That will trigger BUG_ON in clear_inode!
Fix it by checking PageWriteback too to help determine should we skip
wait_on_page_writeback.
Affected
18 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.10.46-1 (bookworm) | linux 5.10.46-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 0bc1f8b0682caa39f45ce1e0228ebf43acb46111 < d05267fd27a5c4f54e06daefa3035995d765ca0c | d05267fd27a5c4f54e06daefa3035995d765ca0c |
| linux | linux | >= 0bc1f8b0682caa39f45ce1e0228ebf43acb46111 < 6d210d547adc2218ef8b5bcf23518c5f2f1fd872 | 6d210d547adc2218ef8b5bcf23518c5f2f1fd872 |
| linux | linux | >= 0bc1f8b0682caa39f45ce1e0228ebf43acb46111 < 566345aaabac853aa866f53a219c4b02a6beb527 | 566345aaabac853aa866f53a219c4b02a6beb527 |
| linux | linux | >= 0bc1f8b0682caa39f45ce1e0228ebf43acb46111 < 9e379da727a7a031be9b877cde7b9c34a0fb8306 | 9e379da727a7a031be9b877cde7b9c34a0fb8306 |
| linux | linux | >= 0bc1f8b0682caa39f45ce1e0228ebf43acb46111 < 28788dc5c70597395b6b451dae4549bbaa8e2c56 | 28788dc5c70597395b6b451dae4549bbaa8e2c56 |
| linux | linux | >= 0bc1f8b0682caa39f45ce1e0228ebf43acb46111 < e8675d291ac007e1c636870db880f837a9ea112a | e8675d291ac007e1c636870db880f837a9ea112a |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 3.16 < 4.14.238 | 4.14.238 |
| linux | linux_kernel | >= 4.15 < 4.19.196 | 4.19.196 |
| linux | linux_kernel | >= 4.20 < 5.4.128 | 5.4.128 |
| linux | linux_kernel | >= 5.11 < 5.12.13 | 5.12.13 |
| linux | linux_kernel | >= 5.5 < 5.10.46 | 5.10.46 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-p52g-5qgx-4crw: In the Linux kernel, the following vulnerability has been resolved:
mm/memory-failure: make sure wait for page writeback in memory_failure
Our syzka
ghsa_unreviewed·2024-05-21
CVE-2021-47256 [MEDIUM] GHSA-p52g-5qgx-4crw: In the Linux kernel, the following vulnerability has been resolved:
mm/memory-failure: make sure wait for page writeback in memory_failure
Our syzka
In the Linux kernel, the following vulnerability has been resolved:
mm/memory-failure: make sure wait for page writeback in memory_failure
Our syzkaller trigger the "BUG_ON(!list_empty(&inode->i_wb_list))" in
clear_inode:
kernel BUG at fs/inode.c:519!
Internal error: Oops - BUG: 0 [#1] SMP
Modules linked in:
Process syz-executor.0 (pid: 249, stack limit = 0x00000000a12409d7)
CPU: 1 PID: 249 Comm: syz-executor.0 Not tainted 4.19.95
Hardware name: linux,dummy-virt (DT)
pstate: 80000005 (Nzcv daif -PAN -UAO)
pc : clear_inode+0x280/0x2a8
lr : clear_inode+0x280/0x2a8
Call trace:
clear_inode+0x280/0x2a8
ext4_clear_inode+0x38/0xe8
ext4_free_inode+0x130/0xc68
ext4_evict_inode+0xb20/0xcb8
evict+0x1a8/0x3c0
iput+0x344/0x460
do_unlinkat+0x260/0x410
__arm64_sys_unlinkat+0x6c/0xc0
el0_svc_common+0xd
OSV
CVE-2021-47256: In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: make sure wait for page writeback in memory_failure Our syzkall
osv·2024-05-21·CVSS 5.5
CVE-2021-47256 [MEDIUM] CVE-2021-47256: In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: make sure wait for page writeback in memory_failure Our syzkall
In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: make sure wait for page writeback in memory_failure Our syzkaller trigger the "BUG_ON(!list_empty(&inode->i_wb_list))" in clear_inode: kernel BUG at fs/inode.c:519! Internal error: Oops - BUG: 0 [#1] SMP Modules linked in: Process syz-executor.0 (pid: 249, stack limit = 0x00000000a12409d7) CPU: 1 PID: 249 Comm: syz-executor.0 Not tainted 4.19.95 Hardware name: linux,dummy-virt (DT) pstate: 80000005 (Nzcv daif -PAN -UAO) pc : clear_inode+0x280/0x2a8 lr : clear_inode+0x280/0x2a8 Call trace: clear_inode+0x280/0x2a8 ext4_clear_inode+0x38/0xe8 ext4_free_inode+0x130/0xc68 ext4_evict_inode+0xb20/0xcb8 evict+0x1a8/0x3c0 iput+0x344/0x460 do_unlinkat+0x260/0x410 __arm64_sys_unlinkat+0x6c/0xc0 el0_svc_common+0xdc/0
Red Hat
kernel: mm/memory-failure: make sure wait for page writeback in memory_failure
vendor_redhat·2024-05-21·CVSS 5.5
CVE-2021-47256 [MEDIUM] CWE-567 kernel: mm/memory-failure: make sure wait for page writeback in memory_failure
kernel: mm/memory-failure: make sure wait for page writeback in memory_failure
In the Linux kernel, the following vulnerability has been resolved:
mm/memory-failure: make sure wait for page writeback in memory_failure
Our syzkaller trigger the "BUG_ON(!list_empty(&inode->i_wb_list))" in
clear_inode:
kernel BUG at fs/inode.c:519!
Internal error: Oops - BUG: 0 [#1] SMP
Modules linked in:
Process syz-executor.0 (pid: 249, stack limit = 0x00000000a12409d7)
CPU: 1 PID: 249 Comm: syz-executor.0 Not tainted 4.19.95
Hardware name: linux,dummy-virt (DT)
pstate: 80000005 (Nzcv daif -PAN -UAO)
pc : clear_inode+0x280/0x2a8
lr : clear_inode+0x280/0x2a8
Call trace:
clear_inode+0x280/0x2a8
ext4_clear_inode+0x38/0xe8
ext4_free_inode+0x130/0xc68
ext4_evict_inode+0xb20/0xcb8
evict+0x1a8/0x3c0
iput+0x344/0x
Debian
CVE-2021-47256: linux - In the Linux kernel, the following vulnerability has been resolved: mm/memory-f...
vendor_debian·2021·CVSS 5.5
CVE-2021-47256 [MEDIUM] CVE-2021-47256: linux - In the Linux kernel, the following vulnerability has been resolved: mm/memory-f...
In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: make sure wait for page writeback in memory_failure Our syzkaller trigger the "BUG_ON(!list_empty(&inode->i_wb_list))" in clear_inode: kernel BUG at fs/inode.c:519! Internal error: Oops - BUG: 0 [#1] SMP Modules linked in: Process syz-executor.0 (pid: 249, stack limit = 0x00000000a12409d7) CPU: 1 PID: 249 Comm: syz-executor.0 Not tainted 4.19.95 Hardware name: linux,dummy-virt (DT) pstate: 80000005 (Nzcv daif -PAN -UAO) pc : clear_inode+0x280/0x2a8 lr : clear_inode+0x280/0x2a8 Call trace: clear_inode+0x280/0x2a8 ext4_clear_inode+0x38/0xe8 ext4_free_inode+0x130/0xc68 ext4_evict_inode+0xb20/0xcb8 evict+0x1a8/0x3c0 iput+0x344/0x460 do_unlinkat+0x260/0x410 __arm64_sys_unlinkat+0x6c/0xc0 el0_svc_common+0xdc/0
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/28788dc5c70597395b6b451dae4549bbaa8e2c56https://git.kernel.org/stable/c/566345aaabac853aa866f53a219c4b02a6beb527https://git.kernel.org/stable/c/6d210d547adc2218ef8b5bcf23518c5f2f1fd872https://git.kernel.org/stable/c/9e379da727a7a031be9b877cde7b9c34a0fb8306https://git.kernel.org/stable/c/d05267fd27a5c4f54e06daefa3035995d765ca0chttps://git.kernel.org/stable/c/e8675d291ac007e1c636870db880f837a9ea112ahttps://git.kernel.org/stable/c/28788dc5c70597395b6b451dae4549bbaa8e2c56https://git.kernel.org/stable/c/566345aaabac853aa866f53a219c4b02a6beb527https://git.kernel.org/stable/c/6d210d547adc2218ef8b5bcf23518c5f2f1fd872https://git.kernel.org/stable/c/9e379da727a7a031be9b877cde7b9c34a0fb8306https://git.kernel.org/stable/c/d05267fd27a5c4f54e06daefa3035995d765ca0chttps://git.kernel.org/stable/c/e8675d291ac007e1c636870db880f837a9ea112a
2024-05-21
Published