CVE-2023-53151

md/raid10: prevent soft lockup while flush writes

MEDIUM

5.5

CVSS Score

Published: September 15, 2025 at 02:03 PM UTC

Updated: June 17, 2026 at 06:44 AM 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

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: md/raid10: prevent soft lockup while flush writes Currently, there is no limit for raid1/raid10 plugged bio. While flushing writes, raid1 has cond_resched() while raid10 doesn't, and too many writes can cause soft lockup. Follow up soft lockup can be triggered easily with writeback test for raid10 with ramdisks: watchdog: BUG: soft lockup - CPU#10 stuck for 27s! [md0_raid10:1293] Call Trace: <TASK> call_rcu+0x16/0x20 put_object+0x41/0x80 __delete_object+0x50/0x90 delete_object_full+0x2b/0x40 kmemleak_free+0x46/0xa0 slab_free_freelist_hook.constprop.0+0xed/0x1a0 kmem_cache_free+0xfd/0x300 mempool_free_slab+0x1f/0x30 mempool_free+0x3a/0x100 bio_free+0x59/0x80 bio_put+0xcf/0x2c0 free_r10bio+0xbf/0xf0 raid_end_bio_io+0x78/0xb0 one_write_done+0x8a/0xa0 raid10_end_write_request+0x1b4/0x430 bio_endio+0x175/0x320 brd_submit_bio+0x3b9/0x9b7 [brd] __submit_bio+0x69/0xe0 submit_bio_noacct_nocheck+0x1e6/0x5a0 submit_bio_noacct+0x38c/0x7e0 flush_pending_writes+0xf0/0x240 raid10d+0xac/0x1ed0 Fix the problem by adding cond_resched() to raid10 like what raid1 did. Note that unlimited plugged bio still need to be optimized, for example, in the case of lots of dirty pages writeback, this will take lots of memory and io will spend a long time in plug, hence io latency is bad.

Affected

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

Linux Kernel · Linux

95%

v < 4.14.3222.6.16 ≤ v < 4.14.3222.6.16 ≤ v < 4.19.2912.6.16 ≤ v < 5.10.1882.6.16 ≤ v < 5.15.1502.6.16 ≤ v < 5.4.2512.6.16 ≤ v < 6.1.832.6.16 ≤ v < 6.4.72.6.16 ≤ v < 6.54.15 ≤ v < 4.19.2914.20 ≤ v < 5.4.2515.11 ≤ v < 5.15.1505.16 ≤ v < 6.1.835.5 ≤ v < 5.10.1886.2 ≤ v < 6.4.72.6.166cce3b23f6f8e974c00af7a9b88f1d413ba368a8

Vendor states this is fixed in 00ecb6fa67c0f772290c5ea5ae8b46eefd503b83 (fixed)

Vendor states this is fixed in 010444623e7f4da6b4a4dd603a7da7469981e293 (fixed)

Vendor states this is fixed in 1d467e10507167eb6dc2c281a87675b731955d86 (fixed)

Vendor states this is fixed in 634daf6b2c81015cc5e28bf694a6a94a50c641cd (fixed)

Vendor states this is fixed in 84a578961b2566e475bfa8740beaf0abcc781a6f (fixed)

Vendor states this is fixed in d0345f7c7dbc5d42e4e6f1db99c1c1879d7b0eb5 (fixed)

Vendor states this is fixed in f45b2fa7678ab385299de345f7e85d05caea386b (fixed)

Vendor states this is fixed in fbf50184190d55f8717bd29aa9530c399be96f30 (fixed)

Vendor states this is fixed in 2.6.16 (unaffected)

Vendor states this is fixed in 4.14.322 (unaffected)

Vendor states this is fixed in 4.19.291 (unaffected)

Vendor states this is fixed in 5.10.188 (unaffected)