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.
[
{
"product": "Linux",
"vendor": "Linux",
"defaultStatus": "unaffected",
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"programFiles": [
"drivers/md/dm-raid.c"
],
"versions": [
{
"version": "be83651f0050",
"lessThan": "347dcdc15a17",
"status": "affected",
"versionType": "git"
},
{
"version": "be83651f0050",
"lessThan": "9e59b8d76ff5",
"status": "affected",
"versionType": "git"
},
{
"version": "be83651f0050",
"lessThan": "cd32b27a66db",
"status": "affected",
"versionType": "git"
}
]
},
{
"product": "Linux",
"vendor": "Linux",
"defaultStatus": "affected",
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"programFiles": [
"drivers/md/dm-raid.c"
],
"versions": [
{
"version": "3.10",
"status": "affected"
},
{
"version": "0",
"lessThan": "3.10",
"status": "unaffected",
"versionType": "custom"
},
{
"version": "6.7.12",
"lessThanOrEqual": "6.7.*",
"status": "unaffected",
"versionType": "custom"
},
{
"version": "6.8.3",
"lessThanOrEqual": "6.8.*",
"status": "unaffected",
"versionType": "custom"
},
{
"version": "6.9",
"lessThanOrEqual": "*",
"status": "unaffected",
"versionType": "original_commit_for_fix"
}
]
}
]