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-89834f2fs: fix to migrate all curseg types during free_segment_range

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to migrate all curseg types during free_segment_range In free_segment_range(), the curseg evacuation loop only iterates up to NR_CURSEG_PERSIST_TYPE (0..5), missing non-persistent in-memory curseg types such as CURSEG_COLD_DATA_PINNED and CURSEG_ALL_DATA_ATGC. Even though these in-memory curseg types are not saved in the on-disk checkpoint header, they still occupy active physical segments at runtime. If an active in-memory curseg happens to be allocated within the segment range being truncated during filesystem shrink, failing to evacuate it will cause subsequent writes to the curseg attempting out-of-bounds I/O on the truncated storage range. Fix this by expanding the curseg evacuation loop upper bound to NR_CURSEG_TYPE to ensure all active curseg types are safely migrated out of the target range.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 44 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.21% · top 88% of all CVEs (13 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 d0b9e42ab6155dc05fc83f00af9f45d4dd02264d – < 7ffac0deea2d84cf79051f16fed8e215c4bcf0e6
    • affected d0b9e42ab6155dc05fc83f00af9f45d4dd02264d – < d358d2fc6be11eefde5eb1286f1c43a6d0330db6
    • affected d0b9e42ab6155dc05fc83f00af9f45d4dd02264d – < 3b85edf3391f3e1f624f409a7d2d239885f567b7
    • affected d0b9e42ab6155dc05fc83f00af9f45d4dd02264d – < b8ae1228c153622afa71a179c9d4dc268117e0f0
    • affected d0b9e42ab6155dc05fc83f00af9f45d4dd02264d – < b9776094aa7118e8e5dfdcd791ffc8330c5ca408
    • affected d0b9e42ab6155dc05fc83f00af9f45d4dd02264d – < 8ec06f50ddd8d201bd7e55b896ae28ed9d4cb7d1
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 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-89834 badge
[![CVE-2026-89834](https://cveledger.app/badge/CVE-2026-89834.svg)](https://cveledger.app/cve/CVE-2026-89834)

Record last updated .