Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 378949f46e897204384f3f5f91e42e93e3f87568, 5c8ecdcfbfb0b0c6a82a4ebadc1ddea61609b902, c23df30915f83e7257c8625b690a1cece94142a0; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2.

Low priority for now. Upgrade to Linux Linux 378949f46e897204384f3f5f91e42e93e3f87568, 5c8ecdcfbfb0b0c6a82a4ebadc1ddea61609b902, c23df30915f83e7257c8625b690a1cece94142a0; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Apr 22, 2026
Updated
Aug 5, 2026
EPSS
0.3% · 31th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CNA vs NVD score

NVD
—
CNA · Linux
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-31467

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.13 and later · before 5.15.203
  • linux linux kernel5.16 and later · before 6.1.168
  • linux linux kernel6.2 and later · before 6.6.131
  • linux linux kernel6.7 and later · before 6.12.80
  • linux linux kernel6.13 and later · before 6.18.21
  • linux linux kernel6.19 and later · before 6.19.11
  • linux linux kernel7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.13affected
    • 648f2de053a882c87c05f0060f47d3b11841fdbe and later · before d6565ea662e17d45a577184b0011bd69de22dc2baffected · git
    • 648f2de053a882c87c05f0060f47d3b11841fdbe and later · before d9d8360cb66e3b599d89d2526e7da8b530ebf2ffaffected · git
    • 648f2de053a882c87c05f0060f47d3b11841fdbe and later · before 5c8ecdcfbfb0b0c6a82a4ebadc1ddea61609b902affected · git
    • 648f2de053a882c87c05f0060f47d3b11841fdbe and later · before 378949f46e897204384f3f5f91e42e93e3f87568affected · git
    • 648f2de053a882c87c05f0060f47d3b11841fdbe and later · before da40464064599eefe78749f75cd2bba371044c04affected · git
    • 648f2de053a882c87c05f0060f47d3b11841fdbe and later · before e83e20b82859f0588e9a52a6fa9fea704a2061cfaffected · git
    • 648f2de053a882c87c05f0060f47d3b11841fdbe and later · before c23df30915f83e7257c8625b690a1cece94142a0affected · git
    • before 5.13not affected · semver
    • 5.15.203 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-31463Apr 22, 2026 · iomap: fix invalid folio access when i_blkbits differs from I/O granularity
    39Monitor
  • ← EarlierCVE-2026-31465Apr 22, 2026 · writeback: don't block sync for filesystems with no data integrity guarantees
    22Monitor
  • Later →CVE-2026-31471Apr 22, 2026 · xfrm: iptfs: only publish mode_data after clone setup
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux378949f46e897204384f3f5f91e42e93e3f87568Vendor (CNA)
Linux Linux5c8ecdcfbfb0b0c6a82a4ebadc1ddea61609b902Vendor (CNA)
Linux Linuxc23df30915f83e7257c8625b690a1cece94142a0Vendor (CNA)
Linux Linuxd6565ea662e17d45a577184b0011bd69de22dc2bVendor (CNA)
Linux Linuxd9d8360cb66e3b599d89d2526e7da8b530ebf2ffVendor (CNA)
Linux Linuxda40464064599eefe78749f75cd2bba371044c04Vendor (CNA)
Linux Linuxe83e20b82859f0588e9a52a6fa9fea704a2061cfVendor (CNA)
azl3 kernel 6.6.130.1-3 on Azure Linux 3.06.6.134.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.170-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records