Linux Kernel up to 6.7.11/6.8.2 dm-raid md/dm-raid: md_reap_sync_thread deadlock

Summaryinfo

A vulnerability has been found in Linux Kernel up to 6.7.11/6.8.2 and classified as critical. This issue affects the function md_reap_sync_thread of the file md/dm-raid: of the component dm-raid. Performing a manipulation results in deadlock. This vulnerability is cataloged as CVE-2024-35808. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.7.11/6.8.2. It has been classified as critical. This affects the function md_reap_sync_thread of the file md/dm-raid: of the component dm-raid. The manipulation with an unknown input leads to a deadlock vulnerability. CWE is classifying the issue as CWE-833. The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock. This is going to have an impact on availability. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2024-35808 since 05/17/2024. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 209785 (EulerOS Virtualization 2.12.0 : kernel (EulerOS-SA-2024-2781)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.7.12 or 6.8.3 eliminates this vulnerability. Applying the patch 347dcdc15a17/9e59b8d76ff5/cd32b27a66db is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (209785) and CERT Bund (WID-SEC-2024-1188). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

• Google Container-Optimized OS
• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• IBM InfoSphere Guardium
• Oracle Linux
• Oracle VM
• NetApp FAS
• EMC Avamar
• IBM SAN Volume Controller
• Dell NetWorker
• IBM FlashSystem
• IBM Security Guardium
• RESF Rocky Linux
• Broadcom Brocade SANnav
• Open Source Linux Kernel
• IBM Business Automation Workflow
• IBM Spectrum Protect Plus
• IBM QRadar SIEM
• Dell Avamar
• Juniper Junos Space
• IBM DB2
• IBM Storage Scale System
• SolarWinds Security Event Manager

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.7.0
• 6.7.1
• 6.7.2
• 6.7.3
• 6.7.4
• 6.7.5
• 6.7.6
• 6.7.7
• 6.7.8
• 6.7.9
• 6.7.10
• 6.7.11
• 6.8.0
• 6.8.1
• 6.8.2

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion