CVE-2024-35808: md/dm-raid: don't call md_reap_sync_thread() directly
First published: Fri May 17 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/kernel | <6.7.12 | 6.7.12 |
| redhat/kernel | <6.8.3 | 6.8.3 |
| redhat/kernel | <6.9 | 6.9 |
| debian/linux | <=5.10.223-1<=5.10.226-1<=6.1.123-1<=6.1.119-1 | 6.12.11-1 6.12.12-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/347dcdc15a1706f61aa545ae498ededdf31aeebc
- https://git.kernel.org/stable/c/9e59b8d76ff511505eb0dd1478329f09e0f04669
- https://git.kernel.org/stable/c/cd32b27a66db8776d8b8e82ec7d7dde97a8693b0
- https://launchpad.net/bugs/cve/CVE-2024-35808
- https://access.redhat.com/security/cve/CVE-2024-35808
- https://lore.kernel.org/linux-cve-announce/2024051740-CVE-2024-35808-2bf6@gregkh/T
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2281220
- https://access.redhat.com/errata/RHSA-2024:9315
- https://bugzilla.redhat.com/show_bug.cgi?id=2281219
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-35808
- https://nvd.nist.gov/vuln/detail/CVE-2024-35808
- https://security-tracker.debian.org/tracker/CVE-2024-35808
- https://ubuntu.com/security/CVE-2024-35808
- https://git.kernel.org/linus/cd32b27a66db8776d8b8e82ec7d7dde97a8693b0
Frequently Asked Questions
What is the severity of CVE-2024-35808?
CVE-2024-35808 has been rated with high severity due to its potential to lead to data corruption or system instability.
How do I fix CVE-2024-35808?
To resolve CVE-2024-35808, you should upgrade to kernel versions 6.7.12, 6.8.3, 6.9, or the specified Debian versions 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1.
What systems are affected by CVE-2024-35808?
CVE-2024-35808 affects specific versions of the Linux kernel, including Red Hat kernel and Debian Linux packages.
What causes CVE-2024-35808?
CVE-2024-35808 is caused by a race condition due to the unsafe direct call of md_reap_sync_thread() without holding 'reconfig_mutex'.
Is there a workaround for CVE-2024-35808?
There is no recommended workaround for CVE-2024-35808, so applying the available patches is essential.
- agent/title
- agent/type
- collector/nvd-api
- source/NVD
- collector/epss-latest
- source/FIRST
- agent/epss
- agent/remedy
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/author
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2024-35808
- agent/software-canonical-lookup
- collector/usn-cve
- source/Ubuntu
- agent/event
- collector/nvd-cve
- collector/mitre-cve
- source/MITRE
- agent/description
- agent/severity
- agent/last-modified-date
- agent/references
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- collector/security-tracker-debian
- source/Debian
- package-manager/redhat
- package-manager/debian