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-89567jbd2: bound shrinker scans by examined checkpoint buffers

Description

In the Linux kernel, the following vulnerability has been resolved: jbd2: bound shrinker scans by examined checkpoint buffers The jbd2 shrinker currently accounts only checkpoint buffers that it successfully releases against nr_to_scan. Busy buffers therefore do not consume the scan budget. If a checkpoint transaction contains mostly busy buffers, the shrinker can scan its entire checkpoint list while holding journal->j_list_lock. Large checkpoint lists can result in excessive lock hold times and leave other CPUs spinning on j_list_lock, causing soft lockups or RCU stalls. Pass nr_to_scan into journal_shrink_one_cp_list() and decrement it for every buffer examined, including busy buffers. Pass NULL from checkpoint cleanup paths so their existing full-list behavior is preserved. This restores the scan-budget semantics that existed before journal_shrink_one_cp_list() was changed to always scan a complete checkpoint list.

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 – < 6b5366ba63a58819396045ab146bd37ff9e503c6
    • affected b98dba273a0e47dbfade89c9af73c5b012a4eabb – < edf5fcd0469b7467bd5b37a79502c8d9c3257dbb
    • affected b98dba273a0e47dbfade89c9af73c5b012a4eabb – < 71c6b872c746465fa4b5def239cb296173ca8216
    • affected b98dba273a0e47dbfade89c9af73c5b012a4eabb – < c2c0fb364685b8996c357d3b050394959b29d6e0
    • affected b98dba273a0e47dbfade89c9af73c5b012a4eabb – < 15cb16496446b94e67f7abcb049b8e2c75cd3d02
    • 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-89567 badge
[![CVE-2026-89567](https://cveledger.app/badge/CVE-2026-89567.svg)](https://cveledger.app/cve/CVE-2026-89567)

Record last updated .