CVE-2023-53051: dm crypt: add cond_resched() to dmcrypt_write()

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-05-02 · updated 2026-06-17
Weakness: CWE-835

Description

In the Linux kernel, the following vulnerability has been resolved: dm crypt: add cond_resched() to dmcrypt_write() The loop in dmcrypt_write may be running for unbounded amount of time, thus we need cond_resched() in it. This commit fixes the following warning: [ 3391.153255][ C12] watchdog: BUG: soft lockup - CPU#12 stuck for 23s! [dmcrypt_write/2:2897] ... [ 3391.387210][ C12] Call trace: [ 3391.390338][ C12] blk_attempt_bio_merge.part.6+0x38/0x158 [ 3391.395970][ C12] blk_attempt_plug_merge+0xc0/0x1b0 [ 3391.401085][ C12] blk_mq_submit_bio+0x398/0x550 [ 3391.405856][ C12] submit_bio_noacct+0x308/0x380 [ 3391.410630][ C12] dmcrypt_write+0x1e4/0x208 [dm_crypt] [ 3391.416005][ C12] kthread+0x130/0x138 [ 3391.419911][ C12] ret_from_fork+0x10/0x18

Affected products

Linux kernel: from 4.0 before 4.14.312; from 4.15 before 4.19.280; from 4.20 before 5.4.240; from 5.5 before 5.10.177; from 5.11 before 5.15.105; from 5.16 before 6.1.22 — fixed in 4.14.312, 4.19.280, 5.10.177, 5.15.105, 5.4.240, 6.1.22

How to fix

Upgrade to a fixed version: Linux kernel 4.14.312, 4.19.280, 5.10.177, 5.15.105. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2023-53051 or the next vulnerability affects your stack