CVE-2026-31467
MEDIUMDescription
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.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 31% of all known CVEs.
References
Related Vulnerabilities
Other CWE-667 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-10072 | High | 7.5 | 73% | - | Fix |
| CVE-2002-1850 | High | 7.5 | 17% | - | Fix |
| CVE-2009-2699 | High | 7.5 | 14% | - | Fix |
| CVE-2004-0174 | High | 7.5 | 12% | - | - |
| CVE-2009-4272 | High | 7.5 | 11% | - | - |
| CVE-2020-24606 | High | 8.6 | 5.2% | - | Fix |
Common questions
How do I fix CVE-2026-31467?
Published advisories record a fix for 427 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-31467 being actively exploited?
Not that we know of. CVE-2026-31467 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.38% is the estimated probability that it will be exploited in the next 30 days. That is higher than 31% of all scored CVEs.
How severe is CVE-2026-31467?
CVE-2026-31467 has a CVSS v3 base score of 5.5, rated moderate. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-31467 affect?
Published advisories record a fix for linux (Debian), kernel (Red Hat / RHEL), kernel (Rocky), kernel-64k (Red Hat / RHEL), and 423 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-31467
Markdown
[](https://tridentstack.com/cve/CVE-2026-31467)HTML
<a href="https://tridentstack.com/cve/CVE-2026-31467"><img src="https://tridentstack.com/cve/badge/CVE-2026-31467.svg" alt="CVE-2026-31467"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-05-07.