md/dm-raid: don't call md_reap_sync_thread() directly
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 347dcdc15a1706f61aa545ae498ededdf31aeebc, Kernel 9e59b8d76ff511505eb0dd1478329f09e0f04669 and Kernel cd32b27a66db8776d8b8e82ec7d7dde97a8693b0.
In the Linux kernel, the following vulnerability has been resolved: md/dm-raid: don't call md_reap_sync_thread() directly Currently md_reap_sync_thread() is called from raid_message() directly without holding 'reconfig_mutex', this is definitely unsafe because md_reap_sync_thread() can change many fields that is protected by 'reconfig_mutex'. However, hold 'reconfig_mutex' here is still problematic because this will cause deadlock, for example, commit 130443d60b1b ("md: refactor idle/frozen_sync_thread() to fix deadlock"). Fix this problem by using stop_sync_thread() to unregister sync_thread, like md/raid did.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.10, >=be83651f0050ca8621d58d35dad558e9c45cb18f <347dcdc15a1706f61aa545ae498ededdf31aeebc, >=be83651f0050ca8621d58d35dad558e9c45cb18f <9e59b8d76ff511505eb0dd1478329f09e0f04669, >=be83651f0050ca8621d58d35dad558e9c45cb18f <cd32b27a66db8776d8b8e82ec7d7dde97a8693b0 | 347dcdc15a1706f61aa545ae498ededdf31aeebc, 9e59b8d76ff511505eb0dd1478329f09e0f04669, cd32b27a66db8776d8b8e82ec7d7dde97a8693b0 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket