CVE-2026-31514: erofs: set fileio bio failed in short read case
Noroxi assessment
Priority: Monitor (action score 22/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.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 5a5f23ef5431639db1ac3a0b274aef3a84cc413c, 5cf3972c8221abdb1b464a14ccf8103d840b9085, d1ba7d6b3cd1757b108d7b6856c92ae661d6c323.
Low priority for now. Upgrade to Linux Linux 5a5f23ef5431639db1ac3a0b274aef3a84cc413c, 5cf3972c8221abdb1b464a14ccf8103d840b9085, d1ba7d6b3cd1757b108d7b6856c92ae661d6c323 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: set fileio bio failed in short read case For file-backed mount, IO requests are handled by vfs_iocb_iter_read(). However, it can be interrupted by SIGKILL, returning the number of bytes actually copied. Unused folios in bio are unexpectedly marked as uptodate. vfs_read filemap_read filemap_get_pages filemap_readahead erofs_fileio_readahead erofs_fileio_rq_submit vfs_iocb_iter_read filemap_read filemap_get_pages <= detect signal erofs_fileio_ki_complete <= set all folios uptodate This patch addresses this by setting short read bio with an error directly.
- Published
- Apr 22, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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
- 6.12affected
- ce63cb62d794c98c7631c2296fa845f2a8d0a4a1 and later · before d1ba7d6b3cd1757b108d7b6856c92ae661d6c323affected · git
- ce63cb62d794c98c7631c2296fa845f2a8d0a4a1 and later · before 5cf3972c8221abdb1b464a14ccf8103d840b9085affected · git
- ce63cb62d794c98c7631c2296fa845f2a8d0a4a1 and later · before 5a5f23ef5431639db1ac3a0b274aef3a84cc413caffected · git
- ce63cb62d794c98c7631c2296fa845f2a8d0a4a1 and later · before eade54040384f54b7fb330e4b0975c5734850b3caffected · git
- before 6.12not affected · semver
- 6.12.80 and later · up to and including 6.12.*not affected · semver
- 6.18.21 and later · up to and including 6.18.*not affected · semver
- 6.19.11 and later · up to and including 6.19.*not affected · semver
- 7.0 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.12.75 and later · before 6.12.80
- linux linux kernel6.18.14 and later · before 6.18.21
- linux linux kernel6.19.4 and later · before 6.19.11
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 6.19.11-1 | 6.19.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-31512Apr 22, 2026 · Bluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv()22Monitor
- ← EarlierCVE-2026-31513Apr 22, 2026 · Bluetooth: L2CAP: Fix stack-out-of-bounds read in l2cap_ecred_conn_req32Monitor
- Later →CVE-2026-31515Apr 22, 2026 · af_key: validate families in pfkey_send_migrate()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 5a5f23ef5431639db1ac3a0b274aef3a84cc413c | Vendor (CNA) |
| Linux Linux | 5cf3972c8221abdb1b464a14ccf8103d840b9085 | Vendor (CNA) |
| Linux Linux | d1ba7d6b3cd1757b108d7b6856c92ae661d6c323 | Vendor (CNA) |
| Linux Linux | eade54040384f54b7fb330e4b0975c5734850b3c | Vendor (CNA) |
| debian:linux | 6.19.11-1 · Debian:14 | Package registry (OSV) |
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- 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
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.