Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-31467erofs: add GFP_NOIO in the bio completion if needed

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 44 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31467, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Analyzed3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.38% · top 68% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected 648f2de053a882c87c05f0060f47d3b11841fdbe – < d6565ea662e17d45a577184b0011bd69de22dc2b
    • affected 648f2de053a882c87c05f0060f47d3b11841fdbe – < d9d8360cb66e3b599d89d2526e7da8b530ebf2ff
    • affected 648f2de053a882c87c05f0060f47d3b11841fdbe – < 5c8ecdcfbfb0b0c6a82a4ebadc1ddea61609b902
    • affected 648f2de053a882c87c05f0060f47d3b11841fdbe – < 378949f46e897204384f3f5f91e42e93e3f87568
    • affected 648f2de053a882c87c05f0060f47d3b11841fdbe – < da40464064599eefe78749f75cd2bba371044c04
    • affected 648f2de053a882c87c05f0060f47d3b11841fdbe – < e83e20b82859f0588e9a52a6fa9fea704a2061cf
    • affected 648f2de053a882c87c05f0060f47d3b11841fdbe – < c23df30915f83e7257c8625b690a1cece94142a0
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.131 – ≤ 6.6.*
    • unaffected 6.12.80 – ≤ 6.12.*
    • unaffected 6.18.21 – ≤ 6.18.*
    • unaffected 6.19.11 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31467 badge
[![CVE-2026-31467](https://cveledger.app/badge/CVE-2026-31467.svg)](https://cveledger.app/cve/CVE-2026-31467)

Record last updated .