nilfs2: fix shift-out-of-bounds due to too large exponent of block 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.20% (FIRST EPSS).
- Fixed version: Linux Linux 8b6ef451b5701b37d9a5905534595776a662edfc, a16731fa1b96226c75bbf18e73513b14fc318360, ddb6615a168f97b91175e00eda4c644741cf531c.
Low priority for now. Upgrade to Linux Linux 8b6ef451b5701b37d9a5905534595776a662edfc, a16731fa1b96226c75bbf18e73513b14fc318360, ddb6615a168f97b91175e00eda4c644741cf531c 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: nilfs2: fix shift-out-of-bounds due to too large exponent of block size If field s_log_block_size of superblock data is corrupted and too large, init_nilfs() and load_nilfs() still can trigger a shift-out-of-bounds warning followed by a kernel panic (if panic_on_warn is set): shift exponent 38973 is too large for 32-bit type 'int' Call Trace: <TASK> dump_stack_lvl+0xcd/0x134 ubsan_epilogue+0xb/0x50 __ubsan_handle_shift_out_of_bounds.cold.12+0x17b/0x1f5 init_nilfs.cold.11+0x18/0x1d [nilfs2] nilfs_mount+0x9b5/0x12b0 [nilfs2] ... This fixes the issue by adding and using a new helper function for getting block size with sanity check.
- Published
- Dec 30, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 9th 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.2%
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
- 2.6.30affected
- 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f and later · before ec93b5430ec0f60877a5388bb023d60624f9ab9faffected · git
- 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f and later · before 8b6ef451b5701b37d9a5905534595776a662edfcaffected · git
- 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f and later · before ddb6615a168f97b91175e00eda4c644741cf531caffected · git
- 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f and later · before a16731fa1b96226c75bbf18e73513b14fc318360affected · git
- 8a9d2191e9f43bbcd256a9a6871bd73434c83f2f and later · before ebeccaaef67a4895d2496ab8d9c2fb8d89201211affected · git
- before 2.6.30not affected · semver
- 5.10.163 and later · up to and including 5.10.*not affected · semver
- 5.15.86 and later · up to and including 5.15.*not affected · semver
- 6.0.16 and later · up to and including 6.0.*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.4-1 | 6.1.4-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-2022-50862Dec 30, 2025 · bpf: prevent decl_tag from being referenced in func_proto0Monitor
- ← EarlierCVE-2022-50863Dec 30, 2025 · wifi: rtw89: free unused skb to prevent memory leak0Monitor
- Later →CVE-2022-50865Dec 30, 2025 · tcp: fix a signed-integer-overflow bug in tcp_add_backlog()30Monitor
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 | 8b6ef451b5701b37d9a5905534595776a662edfc | Vendor (CNA) |
| Linux Linux | a16731fa1b96226c75bbf18e73513b14fc318360 | Vendor (CNA) |
| Linux Linux | ddb6615a168f97b91175e00eda4c644741cf531c | Vendor (CNA) |
| Linux Linux | ebeccaaef67a4895d2496ab8d9c2fb8d89201211 | Vendor (CNA) |
| Linux Linux | ec93b5430ec0f60877a5388bb023d60624f9ab9f | Vendor (CNA) |
| debian:linux | 6.1.4-1 · 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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.