erofs: add GFP_NOIO in the bio completion if needed
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 648f2de053a882c87c05f0060f47d3b11841fdbe · < e83e20b82859f0588e9a52a6fa9fea704a2061cf| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
erofs: add GFP_NOIO in the bio completion if needed
The bio completion path in the process context (e.g. dm-verity) will directly call into decompression rather than trigger another workqueue context for minimal scheduling latencies, which can then call vm_map_ram() with GFP_KERNEL.
Due to insufficient memory, vm_map_ram() may generate memory swapping I/O, which can cause submit_bio_wait to deadlock in some scenarios.
Trimmed down the call stack, as follows:
f2fs_submit_read_io submit_bio //bio_list is initialized. mmc_blk_mq_recovery z_erofs_endio vm_map_ram __pte_alloc_kernel __alloc_pages_direct_reclaim shrink_folio_list __swap_writepage submit_bio_wait //bio_list is non-NULL, hang!!!
Use memalloc_noio_{save,restore}() to wrap up this path.
From the CVE record · Linux
The Linux kernel's EROFS bio completion path can deadlock when decompression calls vm_map_ram() under insufficient memory and memory reclaim triggers swapping I/O. This can hang the system; the input does not establish an attack path or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels that use EROFS should check their kernel's advisory; affected versions were not provided.