CVE-2026-80807: nilfs2: reject invalid block index in GC ioctl
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 3bd064ccc70b85f9a3d53aece29dc8473be5a226, 68aa9ab6f8f2895713aa6ddf781463ed8ea5ba44, 898404cdf882d7b54f1132f75570984ca3214796.
Low priority for now. Upgrade to Linux Linux 3bd064ccc70b85f9a3d53aece29dc8473be5a226, 68aa9ab6f8f2895713aa6ddf781463ed8ea5ba44, 898404cdf882d7b54f1132f75570984ca3214796 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: reject invalid block index in GC ioctl Syzbot reported list corruption caused by a double list_add_tail() call on bh->b_assoc_buffers within nilfs_lookup_dirty_data_buffers(). Analysis revealed that the root cause was the insertion of a page/folio with a page index of ULONG_MAX into the page cache via the GC ioctl. filemap_get_folios_tag(), called by nilfs_lookup_dirty_data_buffers(), repeatedly detects a dirty folio with a page index of ULONG_MAX due to index wrap-around, leading to duplicate processing of dirty buffers. As a preparatory step, the GC ioctl loads the page/folio of the block to be moved during GC and inserts it into the page cache based on information in the nilfs_vdesc structure passed as an argument. Normally, this does not cause issues because the user-space GC library configures the nilfs_vdesc structure properly. However, since there is no range check on the parameters determining the page index, a request with artificially crafted parameters -- such as those generated by Syzbot -- can result in a page/folio being inserted with a page index of ULONG_MAX, triggering the above problem. This resolves the issue by checking the ranges of 'vd_offset' and 'vd_vblocknr' in the nilfs_vdesc structure that determine the page index, thereby preventing the invalid page/folio insertions.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 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
- 7942b919f7321f95a777d396ff7894a7a83dc9b0 and later · before 898404cdf882d7b54f1132f75570984ca3214796affected · git
- 7942b919f7321f95a777d396ff7894a7a83dc9b0 and later · before ba8a8b563a28d358c45c62a306d421434a058648affected · git
- 7942b919f7321f95a777d396ff7894a7a83dc9b0 and later · before 3bd064ccc70b85f9a3d53aece29dc8473be5a226affected · git
- 7942b919f7321f95a777d396ff7894a7a83dc9b0 and later · before a5e776e2937581d67ec5b9b4d27b0f70d7baa6b1affected · git
- 7942b919f7321f95a777d396ff7894a7a83dc9b0 and later · before 68aa9ab6f8f2895713aa6ddf781463ed8ea5ba44affected · git
- 7942b919f7321f95a777d396ff7894a7a83dc9b0 and later · before e447f7edb99bd00cec63d6f3049e2e5074946f71affected · git
- 7942b919f7321f95a777d396ff7894a7a83dc9b0 and later · before ec6ddf271dfa4c7e3147bc2c8b2bad4315f316a1affected · git
- 7942b919f7321f95a777d396ff7894a7a83dc9b0 and later · before fbcfb75c20d71a5b542ad4ac3b79d10b997c8152affected · git
- 7942b919f7321f95a777d396ff7894a7a83dc9b0 and later · before a1735eae55448bc79c2da6593455791e886f6ed8affected · git
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.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.1.12-1 | 7.1.12-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-80805Sep 4, 2026 · xfs: validate attr entry pointer before field access0Monitor
- ← EarlierCVE-2026-80806Sep 4, 2026 · ext4: don't enable DAX on new encrypted files0Monitor
- Later →CVE-2026-80808Sep 4, 2026 · ext4: stop retrying saturated xattr cache entries0Monitor
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 | 3bd064ccc70b85f9a3d53aece29dc8473be5a226 | Vendor (CNA) |
| Linux Linux | 68aa9ab6f8f2895713aa6ddf781463ed8ea5ba44 | Vendor (CNA) |
| Linux Linux | 898404cdf882d7b54f1132f75570984ca3214796 | Vendor (CNA) |
| Linux Linux | a1735eae55448bc79c2da6593455791e886f6ed8 | Vendor (CNA) |
| Linux Linux | a5e776e2937581d67ec5b9b4d27b0f70d7baa6b1 | Vendor (CNA) |
| Linux Linux | ba8a8b563a28d358c45c62a306d421434a058648 | Vendor (CNA) |
| Linux Linux | e447f7edb99bd00cec63d6f3049e2e5074946f71 | Vendor (CNA) |
| Linux Linux | ec6ddf271dfa4c7e3147bc2c8b2bad4315f316a1 | Vendor (CNA) |
| Linux Linux | fbcfb75c20d71a5b542ad4ac3b79d10b997c8152 | 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.111-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 (8 more)Show less
- git.kernel.org/stable/c/68aa9ab6f8f2895713aa6ddf781463ed8ea5ba44
- git.kernel.org/stable/c/898404cdf882d7b54f1132f75570984ca3214796
- git.kernel.org/stable/c/a1735eae55448bc79c2da6593455791e886f6ed8
- git.kernel.org/stable/c/a5e776e2937581d67ec5b9b4d27b0f70d7baa6b1
- git.kernel.org/stable/c/ba8a8b563a28d358c45c62a306d421434a058648
- git.kernel.org/stable/c/e447f7edb99bd00cec63d6f3049e2e5074946f71
- git.kernel.org/stable/c/ec6ddf271dfa4c7e3147bc2c8b2bad4315f316a1
- git.kernel.org/stable/c/fbcfb75c20d71a5b542ad4ac3b79d10b997c8152
Vendor advisories and official records. Exploit/PoC links are deliberately left out.