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.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 20.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux | < 6.8.0-35.35 | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux-aws | < 6.8.0-1009.9 | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws-5.15 | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws-6.5 | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux-azure | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-azure | < any | UNKNOWN |
git.kernel.org/linus/cd32b27a66db8776d8b8e82ec7d7dde97a8693b0 (6.9-rc1)
git.kernel.org/stable/c/347dcdc15a1706f61aa545ae498ededdf31aeebc
git.kernel.org/stable/c/9e59b8d76ff511505eb0dd1478329f09e0f04669
git.kernel.org/stable/c/cd32b27a66db8776d8b8e82ec7d7dde97a8693b0
launchpad.net/bugs/cve/CVE-2024-35808
nvd.nist.gov/vuln/detail/CVE-2024-35808
security-tracker.debian.org/tracker/CVE-2024-35808
ubuntu.com/security/notices/USN-6816-1
ubuntu.com/security/notices/USN-6817-1
ubuntu.com/security/notices/USN-6817-2
ubuntu.com/security/notices/USN-6817-3
ubuntu.com/security/notices/USN-6878-1
www.cve.org/CVERecord?id=CVE-2024-35808