The vulnerability in the Linux kernel jbd2 subsystem was due to the shrinker only accounting for checkpoint buffers it successfully released against the scan budget (nr_to_scan), ignoring busy buffers. When a checkpoint transaction contained mostly busy buffers, the shrinker could scan the entire checkpoint list while holding the journal->j_list_lock for an extended period. Large checkpoint lists could cause excessive lock hold times, leading to other CPUs spinning on the lock and causing soft lockups or RCU stalls. The fix involves passing the scan budget into journal_shrink_one_cp_list() and decrementing it for every buffer examined, including busy buffers, restoring the original scan-budget behavior.

The vulnerability could cause system instability by inducing soft lockups or RCU stalls due to excessive lock hold times on journal->j_list_lock during checkpoint list scanning. This affects CPU scheduling and system responsiveness but does not indicate direct data corruption or privilege escalation.

A fix has been implemented in the Linux kernel to address this issue by properly accounting for all checkpoint buffers during shrinker scans. Users should apply the official kernel updates that include this fix. Since no patch links or vendor advisory details are provided, check the Linux kernel release notes or vendor advisories for the specific fixed versions and update accordingly.