# CVE-2024-35808: md/dm-raid: don't call md_reap_sync_thread() directly

> A race condition in the Linux kernel's md/dm-raid module can lead to system instability or denial of service due to unsafe concurrent access to protected fields.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 May 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-62827, AZL-67587, BELL-CVE-2024-35808, DEBIAN-CVE-2024-35808, GHSA-xx3r-74m7-rjg4, ROOT-OS-DEBIAN-11-CVE-2024-35808, ROOT-OS-DEBIAN-12-CVE-2024-35808, ROOT-OS-UBUNTU-2204-CVE-2024-35808, UBUNTU-CVE-2024-35808

## What is CVE-2024-35808?

CVE-2024-35808 is a high-severity vulnerability in Linux kernel, published on 17 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-667 (Improper Locking)

## Which versions are affected by CVE-2024-35808?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-35808?

Apply the vendor's patch.

## Is CVE-2024-35808 being exploited?

There is no known exploitation of CVE-2024-35808 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-35808 and fix it if it is affected.

What it is: CVE-2024-35808 is a high-severity vulnerability in Linux kernel, published on 17 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-35808 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-35808/ (Markdown: https://insights.sbomify.com/CVE-2024-35808/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-35808
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-35808
- OSV: https://osv.dev/vulnerability/CVE-2024-35808

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-35808/
Summaries are generated and may contain mistakes; the official description above is the record.