CVEvulnerability
CVE-2024-35808
5.5 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2024-05-17
- Last modified
- 2026-08-04
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CVSS 3.1 ([email protected])
- 5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-667
Description
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 configurations
• linux linux kernel (>= 3.10 < 6.7.12)
• linux linux kernel (>= 6.8 < 6.8.3)
Related
Weakness · CWE (1)
- CWE-667 Improper Locking weakness
References
- https://git.kernel.org/stable/c/347dcdc15a1706f61aa545ae498ededdf31aeebc Patch
- https://git.kernel.org/stable/c/9e59b8d76ff511505eb0dd1478329f09e0f04669 Patch
- https://git.kernel.org/stable/c/cd32b27a66db8776d8b8e82ec7d7dde97a8693b0 Patch
- https://git.kernel.org/stable/c/347dcdc15a1706f61aa545ae498ededdf31aeebc Patch
- https://git.kernel.org/stable/c/9e59b8d76ff511505eb0dd1478329f09e0f04669 Patch
- https://git.kernel.org/stable/c/cd32b27a66db8776d8b8e82ec7d7dde97a8693b0 Patch