CVE-2026-31467
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of service disruption.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Weakness
- CWE-667
- Record status
- Analyzed
Affected
- Linux Kernel < 5.15.203
- Linux Kernel < 6.1.168
- Linux Kernel < 6.6.131
- Linux Kernel < 6.12.80
- Linux Kernel < 6.18.21
- Linux Kernel < 6.19.11
- Linux Kernel 7.0
Attack profile CVSS 3.1 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-31467.md and follow it. Check whether this project is affected by CVE-2026-31467. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/378949f46e897204384f3f5f91e42e93e3f87568
- https://git.kernel.org/stable/c/5c8ecdcfbfb0b0c6a82a4ebadc1ddea61609b902
- https://git.kernel.org/stable/c/c23df30915f83e7257c8625b690a1cece94142a0
- https://git.kernel.org/stable/c/d6565ea662e17d45a577184b0011bd69de22dc2b
- https://git.kernel.org/stable/c/d9d8360cb66e3b599d89d2526e7da8b530ebf2ff
- https://git.kernel.org/stable/c/da40464064599eefe78749f75cd2bba371044c04
- https://git.kernel.org/stable/c/e83e20b82859f0588e9a52a6fa9fea704a2061cf
References
- https://git.kernel.org/stable/c/378949f46e897204384f3f5f91e42e93e3f87568
- https://git.kernel.org/stable/c/5c8ecdcfbfb0b0c6a82a4ebadc1ddea61609b902
- https://git.kernel.org/stable/c/c23df30915f83e7257c8625b690a1cece94142a0
- https://git.kernel.org/stable/c/d6565ea662e17d45a577184b0011bd69de22dc2b
- https://git.kernel.org/stable/c/d9d8360cb66e3b599d89d2526e7da8b530ebf2ff
- https://git.kernel.org/stable/c/da40464064599eefe78749f75cd2bba371044c04
- https://git.kernel.org/stable/c/e83e20b82859f0588e9a52a6fa9fea704a2061cf