Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 43 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < 6879c603a8d07af82da83768cc2342a11bd444e5
    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < 5166a21b12f549774f2983fa86d2526ea9e66ace
    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < 4e1f21e7540b25d83f86b50780836ed7d2afcc93
    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < 3904fb0ee741ebbbc27ec8f50a9bb6cd31e8af05
    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < f181155baf0c93a74ebe804c6cecbe970e78ee9e
    • affected 8c26c4e2694a163d525976e804d81cd955bbb40c – < 66f4ad3ce158902e5f98afea93189972ed8750c2
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90418 badge
[![CVE-2026-90418](https://cveledger.app/badge/CVE-2026-90418.svg)](https://cveledger.app/cve/CVE-2026-90418)

Record last updated .