[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025050206-CVE-2023-53051-dff1@gregkh>
Date: Fri, 2 May 2025 17:55:16 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53051: dm crypt: add cond_resched() to dmcrypt_write()
From: Greg Kroah-Hartman <gregkh@...nel.org>
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
The Linux kernel CVE team has assigned CVE-2023-53051 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.0 with commit dc2676210c425ee8e5cb1bec5bc84d004ddf4179 and fixed in 4.14.312 with commit e87cd83f70504f1cd2e428966f353c007d6d2d7f
Issue introduced in 4.0 with commit dc2676210c425ee8e5cb1bec5bc84d004ddf4179 and fixed in 4.19.280 with commit 7b9f8efb5fc888dd938d2964e705b8e00f1dc0f6
Issue introduced in 4.0 with commit dc2676210c425ee8e5cb1bec5bc84d004ddf4179 and fixed in 5.4.240 with commit 885c28ceae7dab2b18c2cc0eb95f1f82b1f629d1
Issue introduced in 4.0 with commit dc2676210c425ee8e5cb1bec5bc84d004ddf4179 and fixed in 5.10.177 with commit 66ff37993dd7e9954b6446237fe2453b380ce40d
Issue introduced in 4.0 with commit dc2676210c425ee8e5cb1bec5bc84d004ddf4179 and fixed in 5.15.105 with commit eb485b7404a281d974bd445ddc5b0b8d5958f371
Issue introduced in 4.0 with commit dc2676210c425ee8e5cb1bec5bc84d004ddf4179 and fixed in 6.1.22 with commit f0eb61b493dbbc32529fbd0d2e945b71b0e47306
Issue introduced in 4.0 with commit dc2676210c425ee8e5cb1bec5bc84d004ddf4179 and fixed in 6.2.9 with commit 2c743db1193bf0e76c73d71ede08bd9b96e6c31d
Issue introduced in 4.0 with commit dc2676210c425ee8e5cb1bec5bc84d004ddf4179 and fixed in 6.3 with commit fb294b1c0ba982144ca467a75e7d01ff26304e2b
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2023-53051
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/md/dm-crypt.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/e87cd83f70504f1cd2e428966f353c007d6d2d7f
https://git.kernel.org/stable/c/7b9f8efb5fc888dd938d2964e705b8e00f1dc0f6
https://git.kernel.org/stable/c/885c28ceae7dab2b18c2cc0eb95f1f82b1f629d1
https://git.kernel.org/stable/c/66ff37993dd7e9954b6446237fe2453b380ce40d
https://git.kernel.org/stable/c/eb485b7404a281d974bd445ddc5b0b8d5958f371
https://git.kernel.org/stable/c/f0eb61b493dbbc32529fbd0d2e945b71b0e47306
https://git.kernel.org/stable/c/2c743db1193bf0e76c73d71ede08bd9b96e6c31d
https://git.kernel.org/stable/c/fb294b1c0ba982144ca467a75e7d01ff26304e2b
Powered by blists - more mailing lists