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-90420nilfs2: fix infinite loop in nilfs_clean_segments()

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 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.22% · top 87% of all CVEs (17 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 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < e3e9367dae1a6392cbb14ab0b2ab5edbf39735c3
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < 217b967ad7887a3e1ebc08f46f6484e081acd4b4
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < 3bcdbdaac884a4baa59716cf9bd9470c75276e2d
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < d7afca8e4efbf4c455b4663c29ae59fde2f1b671
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < c07e5ad6539e7e9350d5c65cbf8adb69d1711b15
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < 1fc6df85b4954b6fda9c351843aaca3c06f66d8d
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < 8cea0bc78ac64cb88da49c07f80bf2cf9fb7aff8
    • affected 9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 – < ce5a5ad1a8330a2fcfdd9ec2ab341be739e89a18
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 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

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .