dm crypt: add cond_resched() to dmcrypt_write()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.0
References 8
git.kernel.org
- stable/c/e87cd83f70504f1cd2e428966f353c007d6d2d7f
- stable/c/7b9f8efb5fc888dd938d2964e705b8e00f1dc0f6
- stable/c/885c28ceae7dab2b18c2cc0eb95f1f82b1f629d1
- stable/c/66ff37993dd7e9954b6446237fe2453b380ce40d
- stable/c/eb485b7404a281d974bd445ddc5b0b8d5958f371
- stable/c/f0eb61b493dbbc32529fbd0d2e945b71b0e47306
- stable/c/2c743db1193bf0e76c73d71ede08bd9b96e6c31d
- stable/c/fb294b1c0ba982144ca467a75e7d01ff26304e2b