CVE-2026-89567

jbd2: bound shrinker scans by examined checkpoint buffers

N/A
Published: September 11, 2026 at 07:44 PM UTC
Updated: October 21, 2026 at 01:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.15.129557fda9ed70ebf8eda2620ba3d746215285a13035fda50e262e65bd553ff777c4b280afd1495a18b6.1.506.4.136.59c31bb2684f8035beca0275349d19d679b679ffbb98dba273a0e47dbfade89c9af73c5b012a4eabb
Vendor states this is fixed in 15cb16496446b94e67f7abcb049b8e2c75cd3d02 (fixed)
Vendor states this is fixed in 71c6b872c746465fa4b5def239cb296173ca8216 (fixed)
Vendor states this is fixed in c2c0fb364685b8996c357d3b050394959b29d6e0 (fixed)
Vendor states this is fixed in edf5fcd0469b7467bd5b37a79502c8d9c3257dbb (fixed)
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.5 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card