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-89566jbd2: check need_resched() when skipping busy checkpoint buffers

Description

In the Linux kernel, the following vulnerability has been resolved: jbd2: check need_resched() when skipping busy checkpoint buffers journal_shrink_one_cp_list() skips busy checkpoint buffers when called with JBD2_SHRINK_BUSY_SKIP. The continue statement on this path also skips the need_resched() check at the end of the loop body. Consequently, when a checkpoint list contains mostly busy buffers, the shrinker can walk the entire list while holding journal->j_list_lock, even when a reschedule has been requested. Large checkpoint lists under memory pressure can therefore cause long lock hold times and leave other CPUs spinning on j_list_lock, resulting in soft lockups or RCU stalls. Route the busy-buffer path through the need_resched() check so that the shrinker can release j_list_lock and reschedule promptly, restoring parity with the clean-buffer path, which already checks need_resched(). This does not change which checkpoint buffers are eligible for removal.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 40 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 89% of all CVEs (18 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 b98dba273a0e47dbfade89c9af73c5b012a4eabb – < dc7ece0b827fe3b748db685fb85cd2fc3710c3f9
    • affected b98dba273a0e47dbfade89c9af73c5b012a4eabb – < f83c23286e54180cdc83a36463a60003534cc290
    • affected b98dba273a0e47dbfade89c9af73c5b012a4eabb – < f9182a85991a0ad5cd2940df6db75f40ad90028c
    • affected b98dba273a0e47dbfade89c9af73c5b012a4eabb – < 595cac7f1b32d009b97f83dd2b2d6a1a445e9bb4
    • affected b98dba273a0e47dbfade89c9af73c5b012a4eabb – < f213e12ff5c9590b1034ae8da0e6d09665c772d0
    • affected 9c31bb2684f8035beca0275349d19d679b679ffb
    • affected 5fda50e262e65bd553ff777c4b280afd1495a18b
    • affected 557fda9ed70ebf8eda2620ba3d746215285a1303
    • affected 5.15.129 – < 5.16
    • affected 6.1.50 – < 6.2
    • affected 6.4.13 – < 6.5
  • Linux · Linux

    • affected 6.5
    • unaffected < 6.5
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .