erofs: cap LZMA stream pool size
Noroxi assessment
Priority: Monitor (action score 0/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.17% (FIRST EPSS).
- Fixed version: Linux Linux 0c676903cb2a61992ded8e7907609cc6b0f11744, 5aaa06dfc10f8398c8807453dbec738ea9af10e4, 682cb3ece37fc5141e73bc726ccf4adb833e5189.
Low priority for now. Upgrade to Linux Linux 0c676903cb2a61992ded8e7907609cc6b0f11744, 5aaa06dfc10f8398c8807453dbec738ea9af10e4, 682cb3ece37fc5141e73bc726ccf4adb833e5189 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: cap LZMA stream pool size fs/erofs/decompressor_lzma.c sizes the module-global MicroLZMA stream pool from num_possible_cpus() when the lzma_streams module parameter is unset, then z_erofs_load_lzma_config() preallocates one image-supplied dictionary per stream, accepting dictionaries up to 8 MiB. On high-CPU systems, a small EROFS image can pin hundreds of MiB of vmalloc-backed decoder state until the erofs module is unloaded. Impact: An EROFS image mounted by the system can pin up to 8 MiB of vmalloc memory per LZMA stream, either as intended or unexpectedly. Bound the default stream count by a new CONFIG_EROFS_FS_ZIP_LZMA_DEFAULT_MAX_STREAMS option, default 16, so the worst-case default preallocation is 128 MiB if the number of CPUs is no less than 16 while preserving the existing per-image dictionary limit. An explicit lzma_streams module parameter is still honoured as-is, so administrators who deliberately size the pool are not affected.
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- 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.
Running WordPress? Scan your site free with WP Lens
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 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.
—
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.16affected
- 622ceaddb7649ca328832f50ba1400af778d75fa and later · before 682cb3ece37fc5141e73bc726ccf4adb833e5189affected · git
- 622ceaddb7649ca328832f50ba1400af778d75fa and later · before e8b3d09aa8889dda9be9cbb3d2f0218c4b9acde4affected · git
- 622ceaddb7649ca328832f50ba1400af778d75fa and later · before 0c676903cb2a61992ded8e7907609cc6b0f11744affected · git
- 622ceaddb7649ca328832f50ba1400af778d75fa and later · before 5aaa06dfc10f8398c8807453dbec738ea9af10e4affected · git
- 622ceaddb7649ca328832f50ba1400af778d75fa and later · before e52da169b8c0d19bb2d803f2a07fe0e5a00462d6affected · git
- 622ceaddb7649ca328832f50ba1400af778d75fa and later · before c9b47e6b23114e939b17f818471c7a46e59006e7affected · git
- before 5.16not affected · semver
- 6.1.184 and later · up to and including 6.1.*not affected · semver
- 6.6.151 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80890Sep 4, 2026 · sctp: reject stale cookies with mismatched verification tags0Monitor
- ← EarlierCVE-2026-80891Sep 4, 2026 · KVM: s390: pci: Validate AIBV and AISB before pinning guest pages0Monitor
- Later →CVE-2026-80893Sep 4, 2026 · mm/hugetlb: fix swap entry corruption when clearing uffd-wp at fork()0Monitor
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 | 0c676903cb2a61992ded8e7907609cc6b0f11744 | Vendor (CNA) |
| Linux Linux | 5aaa06dfc10f8398c8807453dbec738ea9af10e4 | Vendor (CNA) |
| Linux Linux | 682cb3ece37fc5141e73bc726ccf4adb833e5189 | Vendor (CNA) |
| Linux Linux | c9b47e6b23114e939b17f818471c7a46e59006e7 | Vendor (CNA) |
| Linux Linux | e52da169b8c0d19bb2d803f2a07fe0e5a00462d6 | Vendor (CNA) |
| Linux Linux | e8b3d09aa8889dda9be9cbb3d2f0218c4b9acde4 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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 researchersFinders, 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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/5aaa06dfc10f8398c8807453dbec738ea9af10e4
- git.kernel.org/stable/c/682cb3ece37fc5141e73bc726ccf4adb833e5189
- git.kernel.org/stable/c/c9b47e6b23114e939b17f818471c7a46e59006e7
- git.kernel.org/stable/c/e52da169b8c0d19bb2d803f2a07fe0e5a00462d6
- git.kernel.org/stable/c/e8b3d09aa8889dda9be9cbb3d2f0218c4b9acde4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.