Skip to content
Heist/ feed
Back to feed
HighFix available

md/dm-raid: don't call md_reap_sync_thread() directly

Type: advisorySources: OSV

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.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.7.12, 6.8.3
CVEs
CVE-2024-35808
Confirmed fixed CVEs
Not specified
Updated in this feed
5 Nov 2026, 02:12 UTC · Revision 1

Source evidence

md/dm-raid: don't call md_reap_sync_thread() directly

core-osv · Original source

Published 17 May 2024, 13:23 UTC

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.

osv:CVE-2024-35808

Kernel

Fixed versions: 6.7.12, 6.8.3

Complete source record
{
  "id": "a8f3005221aa6c85004e4e294b83751c67329516fee6ba917e4f0dcbef1a6908",
  "url": "https://osv.dev/vulnerability/CVE-2024-35808",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "md/dm-raid: don't call md_reap_sync_thread() directly",
    "summary": "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.",
    "evidence": "osv:CVE-2024-35808",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.7.12",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.8.3",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2024-35808",
      "aliases": [
        "CVE-2024-35808"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "be83651f0050ca8621d58d35dad558e9c45cb18f"
                },
                {
                  "fixed": "347dcdc15a1706f61aa545ae498ededdf31aeebc"
                },
                {
                  "fixed": "9e59b8d76ff511505eb0dd1478329f09e0f04669"
                },
                {
                  "fixed": "cd32b27a66db8776d8b8e82ec7d7dde97a8693b0"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-35808.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "3.10.0"
                },
                {
                  "fixed": "6.7.12"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.8.0"
                },
                {
                  "fixed": "6.8.3"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-35808.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:41.866196208Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/347dcdc15a1706f61aa545ae498ededdf31aeebc",
        "https://git.kernel.org/stable/c/9e59b8d76ff511505eb0dd1478329f09e0f04669",
        "https://git.kernel.org/stable/c/cd32b27a66db8776d8b8e82ec7d7dde97a8693b0",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/35xxx/CVE-2024-35808.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2024-35808",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/35xxx/CVE-2024-35808.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2024-35808",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 509273,
  "published_at": "2024-05-17T13:23:15.515+00:00"
}