CVE-2024-35794: dm-raid: really frozen sync_thread during suspend

Published May 17, 2024
·
Updated

dm-raid: really frozen syncthread during suspend

Affected Software

14 affected componentsFixes available
debian/linux<=5.10.223-1, <=5.10.234-1, <=6.1.129-1, <=6.1.135-1
6.12.25-16.12.27-1
Linux Linux kernel>=4.8<6.7.12
Linux Linux kernel>=6.8<6.8.3
Microsoft azl3 kernel 6.6.104.2-4
Microsoft azl3 kernel 6.6.117.1-1
Microsoft cbl2 kernel 5.15.186.1-1
Microsoft azl3 kernel 6.6.96.2-2
Microsoft azl3 kernel 6.6.112.1-2
Microsoft azl3 kernel 6.6.119.3-1
redhat/kernel<6.7.12
6.7.12
redhat/kernel<6.8.3
6.8.3
redhat/kernel<6.9
6.9
Microsoft azl3 hyperv-daemons 6.6.35.1-1<6.6.35.1-1
6.6.35.1-1
Microsoft azl3 hyperv-daemons 6.6.22.1-2<6.6.35.1-1
6.6.35.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.25-1Fixed in 6.12.27-1
  2. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.7.12
  3. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.8.3
  4. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.9
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.35.1-1
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch f52f5c71f3d4
  7. Configuration

    In raid_postsuspend(), always call md_stop_writes() and use MD_RECOVERY_FROZEN as the condition for md_stop_writes() (the text says the prior condition check in raid_postsuspend() “doesn't look correct”).

    Linux kernel md (raid) MD_RECOVERY_FROZEN usage = Use MD_RECOVERY_FROZEN as the condition for md_stop_writes() in raid_postsuspend(); do not rely on MD_RECOVERY_FROZEN alone to freeze an already-running sync_thread
  8. Configuration

    Fix suspend handling so that reentrant stop_sync_thread() does nothing, and always call md_stop_writes() in raid_postsuspend(); additionally, since stop_sync_thread() is only used for dm-raid in this case, move stop_sync_thread() to md_stop_writes() so dm-raid relies on md_stop_writes() to freeze sync_thread indirectly.

    Linux kernel md (raid) / dm-raid sync_thread stopping during suspend = Always call md_stop_writes() in raid_postsuspend(); move stop_sync_thread() behavior into md_stop_writes()
  9. Configuration

    Disallow raid_message() to change sync_thread status (including setting/clearing MD_RECOVERY_FROZEN) during suspend, because raid_message can set/clear MD_RECOVERY_FROZEN at any time and clearing it while suspended can let a new sync_thread start unexpectedly.

    Linux kernel md (raid) / raid_message() MD_RECOVERY_FROZEN modification during suspend = Disallow raid_message() from changing sync_thread status during suspend
  10. Configuration

    Apply the change described: remove MD_RECOVERY_FROZEN from __md_stop_writes() and ensure dm-raid (which relies on __md_stop_writes() indirectly to freeze sync_thread) still behaves correctly.

    Linux kernel md (raid) / __md_stop_writes() MD_RECOVERY_FROZEN removal from __md_stop_writes() = Remove MD_RECOVERY_FROZEN from __md_stop_writes()

Event History

May 17, 2024
CVE Published
via MITRE·12:25 PM
Data Sourced
via MITRE·12:25 PM
Description
Data Sourced
via NVD·01:15 PM
Description
Data Sourced
via NVD·01:15 PM
RemedySeverityAffected Software
Data Sourced
via Red Hat·08:56 PM
DescriptionSeverityAffected Software
Jun 8, 2024
Data Sourced
via Launchpad·01:15 AM
Description
Sep 11, 2024
Data Sourced
via Microsoft·12:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·12:00 AM
Affected Software
Updated
via Microsoft·12:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Apr 29, 2025
Data Sourced
via Ubuntu·06:21 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-35794?

The severity of CVE-2024-35794 is not specified in the provided information, but vulnerabilities in the Linux kernel often have significant impact.

2

How do I fix CVE-2024-35794?

To fix CVE-2024-35794, upgrade to a patched kernel version: 6.7.12, 6.8.3, or 6.9 for Red Hat and specific versions for Debian.

3

What software is affected by CVE-2024-35794?

CVE-2024-35794 affects certain versions of the Linux kernel from both Red Hat and Debian.

4

Is there a workaround for CVE-2024-35794?

No specific workaround is mentioned for CVE-2024-35794; the recommended action is to upgrade the kernel.

5

Can CVE-2024-35794 lead to system crashes?

The details of CVE-2024-35794 suggest that issues related to the synchronization thread could potentially lead to system instability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203