nilfs2: fix BUG in nilfs_copy_dirty_pages() on dirty state mismatch (CVE-2026-90418) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-90418

nilfs2: fix BUG in nilfs_copy_dirty_pages() on dirty state mismatch

Answer in brief

CVE-2026-90418 records a Unknown severity vulnerability in nilfs2: fix BUG in nilfs_copy_dirty_pages() on dirty state mismatch. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=8c26c4e2694a163d525976e804d81cd955bbb40c <5166a21b12f549774f2983fa86d2526ea9e66ace \|\| >=8c26c4e2694a163d525976e804d81cd955bbb40c <4e1f21e7540b25d83f86b50780836ed7d2afcc93 \|\| >=8c26c4e2694a163d525976e804d81cd955bbb40c <3904fb0ee741ebbbc27ec8f50a9bb6cd31e8af05 \|\| >=8c26c4e2694a163d525976e804d81cd955bbb40c <f181155baf0c93a74ebe804c6cecbe970e78ee9e \|\| >=8c26c4e2694a163d525976e804d81cd955bbb40c <66f4ad3ce158902e5f98afea93189972ed8750c2	5166a21b12f549774f2983fa86d2526ea9e66ace, 4e1f21e7540b25d83f86b50780836ed7d2afcc93, 3904fb0ee741ebbbc27ec8f50a9bb6cd31e8af05, f181155baf0c93a74ebe804c6cecbe970e78ee9e, 66f4ad3ce158902e5f98afea93189972ed8750c2
Linux/Linuxgeneric	3.10	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 5166a21b12f549774f2983fa86d2526ea9e66ace if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix BUG in nilfs_copy_dirty_pages() on dirty state mismatch Syzbot reported a kernel BUG triggered within nilfs_copy_dirty_pages(), which copies dirty DAT file folios/pages to its shadow page cache. The BUG occurs when a retrieved dirty folio/page unexpectedly loses its 'dirty' status. This issue arises because, since the commit referenced below, the 'dirty' flag of a folio/page can be cleared asynchronously after the filesystem detects metadata corruption and transitions to read-only mode. Resolve the issue by returning an -EROFS error if the filesystem has transitioned to read-only mode. Also change the behavior to issue a kernel warning only once instead of triggering a kernel BUG when this unexpected 'dirty' state is detected while the filesystem is not in read-only mode.

Quoted source text, attributed separately from HOL analysis.