CVE-2026-90418
CVE CVE-2026-90418EUVD EUVD-2026-82079Published 2026-09-17T16:09:43.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 8c26c4e2694a163d525976e804d81cd955bbb40c <3904fb0ee741ebbbc27ec8f50a9bb6cd31e8af05; 8c26c4e2694a163d525976e804d81cd955bbb40c <5166a21b12f549774f2983fa86d2526ea9e66ace; patch: 6.6.157; patch: 0; 8c26c4e2694a163d525976e804d81cd955bbb40c <4e1f21e7540b25d83f86b50780836ed7d2afcc93; patch: 7.2.6; 3.10; 8c26c4e2694a163d525976e804d81cd955bbb40c <f181155baf0c93a74ebe804c6cecbe970e78ee9e; patch: 7.3-rc1; patch: 6.18.52; patch: 6.12.110; 8c26c4e2694a163d525976e804d81cd955bbb40c <66f4ad3ce158902e5f98afea93189972ed8750c2
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.