CVE-2026-90420 — nilfs2: fix infinite loop in nilfs_clean_segments()
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix infinite loop in nilfs_clean_segments() syzbot reported a hung task in nilfs_transaction_begin(). This occurs because the cleaner ioctl falls into an infinite loop if nilfs_segctor_construct() repeatedly returns -EROFS (e.g. the device is remounted as read-only after an I/O error). Currently in nilfs_clean_segments(), if err is non-zero, it logs the error and sleeps but doesn't abort when it encounters a terminal error like -EROFS. This causes the thread to loop forever. Fix this by breaking out of the loop if nilfs_segctor_construct() returns -EROFS. This matches the behaviour in nilfs_segctor_write_out(), which also handles -EROFS.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 and < e3e9367dae1a6392cbb14ab0b2ab5edbf39735c3≥ 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 and < 217b967ad7887a3e1ebc08f46f6484e081acd4b4≥ 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 and < 3bcdbdaac884a4baa59716cf9bd9470c75276e2d≥ 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 and < d7afca8e4efbf4c455b4663c29ae59fde2f1b671≥ 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 and < c07e5ad6539e7e9350d5c65cbf8adb69d1711b15≥ 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 and < 1fc6df85b4954b6fda9c351843aaca3c06f66d8d≥ 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 and < 8cea0bc78ac64cb88da49c07f80bf2cf9fb7aff8≥ 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 and < ce5a5ad1a8330a2fcfdd9ec2ab341be739e89a18 and 1 moreversion 2.6.30 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/1fc6df85b4954b6fda9c351843aaca3c06f66d8d
- git.kernel.org/stable/c/8cea0bc78ac64cb88da49c07f80bf2cf9fb7aff8
- git.kernel.org/stable/c/ce5a5ad1a8330a2fcfdd9ec2ab341be739e89a18
- git.kernel.org/stable/c/e3e9367dae1a6392cbb14ab0b2ab5edbf39735c3
- git.kernel.org/stable/c/d7afca8e4efbf4c455b4663c29ae59fde2f1b671
- git.kernel.org/stable/c/217b967ad7887a3e1ebc08f46f6484e081acd4b4
- git.kernel.org/stable/c/3bcdbdaac884a4baa59716cf9bd9470c75276e2d
- git.kernel.org/stable/c/c07e5ad6539e7e9350d5c65cbf8adb69d1711b15
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 4h
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 4h
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 4h
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 4h
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 4h
- Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 4h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-90420 is "nilfs2: fix infinite loop in nilfs_clean_segments()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.