CVE-2026-90418: Linux kernel · nilfs2: fix BUG in nilfs_copy_dirty_pages() on dirty state mismatch
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f181155baf0c93a74ebe804c6cecbe970e78ee9e : update Linux kernel when convenient.
Data as of 30 Oct 2026, 13:04 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f181155baf0c93a74ebe804c6cecbe970e78ee9e, 6879c603a8d07af82da83768cc2342a11bd444e5, 5166a21b12f549774f2983fa86d2526ea9e66ace +3
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available in the Linux kernel versions identified by the fixed commit hashes. Users should update their Linux kernel to a version that includes these fixes to prevent kernel BUGs caused by this issue. No additional mitigation is required beyond applying the official fix.
Description
A bug in the Linux kernel's nilfs2 filesystem was fixed in the function nilfs_copy_dirty_pages(). The bug was triggered when a dirty folio/page unexpectedly lost its 'dirty' status, causing a kernel BUG. This occurs due to asynchronous clearing of the 'dirty' flag after the filesystem detects metadata corruption and switches to read-only mode. The fix returns an -EROFS error if the filesystem is read-only and limits kernel warnings to one occurrence when the unexpected state is detected outside read-only mode.
References
- git.kernel.org/stable/c/6879c603a8d07af82da83768cc2342a11bd444e5 (opens in a new tab)
- git.kernel.org/stable/c/5166a21b12f549774f2983fa86d2526ea9e66ace (opens in a new tab)
- git.kernel.org/stable/c/4e1f21e7540b25d83f86b50780836ed7d2afcc93 (opens in a new tab)
- git.kernel.org/stable/c/3904fb0ee741ebbbc27ec8f50a9bb6cd31e8af05 (opens in a new tab)
- git.kernel.org/stable/c/f181155baf0c93a74ebe804c6cecbe970e78ee9e (opens in a new tab)
- git.kernel.org/stable/c/66f4ad3ce158902e5f98afea93189972ed8750c2 (opens in a new tab)