CVE-2026-31467

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

April 22, 2026

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated May 7, 2026
No patch confirmed yet.
generic

erofs: add GFP_NOIO in the bio completion if needed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e83e20b82859f0588e9a52a6fa9fea704a2061cf
generic

erofs: add GFP_NOIO in the bio completion if needed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/da40464064599eefe78749f75cd2bba371044c04
generic

erofs: add GFP_NOIO in the bio completion if needed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d9d8360cb66e3b599d89d2526e7da8b530ebf2ff
generic

erofs: add GFP_NOIO in the bio completion if needed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d6565ea662e17d45a577184b0011bd69de22dc2b
generic

erofs: add GFP_NOIO in the bio completion if needed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c23df30915f83e7257c8625b690a1cece94142a0
generic

erofs: add GFP_NOIO in the bio completion if needed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5c8ecdcfbfb0b0c6a82a4ebadc1ddea61609b902
generic

erofs: add GFP_NOIO in the bio completion if needed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/378949f46e897204384f3f5f91e42e93e3f87568

Vendor Advisories for CVE-2026-31467(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-211.22.1.el10_22026-06-11redhat
linuxKernel @ 5.15.203osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(23)

Data Freshness Timeline

(refreshed 5× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 255 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-02 14:11 UTCEPSS rescore
  11. 2026-09-02 03:04 UTCOSV refresh
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 14:17 UTCEPSS rescore
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 06:00 UTCEG score recompute
  6. 2026-08-16 06:00 UTCVendor advisory
  7. 2026-08-16 06:00 UTCGHSA enrichment
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-14 17:06 UTCVendor advisory
  11. 2026-08-14 17:06 UTCGHSA enrichment
  12. 2026-08-14 04:19 UTCEG score recompute
  13. 2026-08-14 04:19 UTCVendor advisory
  14. 2026-08-14 04:19 UTCGHSA enrichment
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-13 08:39 UTCVendor advisory
  17. 2026-08-13 08:39 UTCGHSA enrichment
  18. 2026-08-12 18:32 UTCEG score recompute
  19. 2026-08-12 18:32 UTCVendor advisory
  20. 2026-08-12 18:32 UTCGHSA enrichment
  21. 2026-08-12 13:50 UTCEPSS rescore
  22. 2026-08-11 16:47 UTCEG score recompute
  23. 2026-08-11 16:47 UTCVendor advisory
  24. 2026-08-11 16:47 UTCGHSA enrichment
  25. 2026-08-11 02:22 UTCEG score recompute
  26. 2026-08-11 02:22 UTCVendor advisory
  27. 2026-08-11 02:22 UTCGHSA enrichment
  28. 2026-08-11 00:00 UTCEPSS rescore
  29. 2026-08-10 03:56 UTCVendor advisory
  30. 2026-08-10 03:56 UTCGHSA enrichment
  31. 2026-08-09 15:45 UTCEG score recompute
  32. 2026-08-09 15:45 UTCVendor advisory
  33. 2026-08-09 15:45 UTCGHSA enrichment
  34. 2026-08-09 13:46 UTCEPSS rescore
  35. 2026-08-09 03:33 UTCEG score recompute
  36. 2026-08-09 03:33 UTCVendor advisory
  37. 2026-08-09 03:33 UTCGHSA enrichment
  38. 2026-08-08 16:37 UTCEPSS rescore
  39. 2026-08-08 01:01 UTCEG score recompute
  40. 2026-08-08 01:01 UTCVendor advisory
  41. 2026-08-08 01:01 UTCGHSA enrichment
  42. 2026-08-07 12:50 UTCEG score recompute
  43. 2026-08-07 12:50 UTCVendor advisory
  44. 2026-08-07 12:49 UTCGHSA enrichment
  45. 2026-08-06 13:46 UTCEPSS rescore
  46. 2026-08-06 13:03 UTCVendor advisory
  47. 2026-08-06 13:03 UTCGHSA enrichment
  48. 2026-08-06 00:51 UTCEG score recompute
  49. 2026-08-06 00:51 UTCVendor advisory
  50. 2026-08-06 00:51 UTCGHSA enrichment
  51. 2026-08-05 19:17 UTCEPSS rescore
  52. 2026-08-05 12:40 UTCEG score recompute
  53. 2026-08-05 12:40 UTCVendor advisory
  54. 2026-08-05 12:40 UTCGHSA enrichment
  55. 2026-08-04 15:10 UTCEPSS rescore
  56. 2026-08-04 10:38 UTCEPSS rescore
  57. 2026-08-03 21:15 UTCEG score recompute
  58. 2026-08-03 21:15 UTCVendor advisory
  59. 2026-08-03 21:15 UTCGHSA enrichment
  60. 2026-08-03 10:36 UTCEPSS rescore
  61. 2026-08-03 00:42 UTCVendor advisory
  62. 2026-08-03 00:42 UTCGHSA enrichment
  63. 2026-08-02 12:30 UTCEG score recompute
  64. 2026-08-02 12:30 UTCVendor advisory
  65. 2026-08-02 12:30 UTCGHSA enrichment
  66. 2026-08-02 02:27 UTCEPSS rescore
  67. 2026-08-01 04:16 UTCEPSS rescore
  68. 2026-07-30 16:27 UTCEPSS rescore
  69. 2026-07-30 01:30 UTCEPSS rescore
  70. 2026-07-28 15:36 UTCEPSS rescore
  71. 2026-07-26 14:54 UTCEPSS rescore
  72. 2026-07-26 14:54 UTCEPSS rescore
  73. 2026-07-25 14:18 UTCEPSS rescore
  74. 2026-07-25 14:17 UTCEPSS rescore
  75. 2026-07-24 14:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-31467?
CVE-2026-31467 is a high vulnerability published on April 22, 2026. 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…
When was CVE-2026-31467 disclosed?
CVE-2026-31467 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31467 actively exploited?
CVE-2026-31467 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.8% of all scored CVEs.
What is the CVSS score of CVE-2026-31467?
CVE-2026-31467 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-31467?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31467, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31467

Explore →

Is Your Infrastructure Affected by CVE-2026-31467?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.