CVE-2024-7409: Qemu: denial of service via improper synchronization in qemu nbd server during socket closure

Published Aug 2, 2024
·
Updated

A flaw was discovered in the qemu code for temporarily exposing an NBD server (used for storage migration and other tasks), where qemu can crash if a client still has a socket open at the time the server is taken offline. Even when qemu is set up to only accept clients with proper TLS credentials, an attacker without the TLS credentials can exploit the flaw by connecting a second socket while a storage migration is ongoing through the intended socket, where the attacker then stalls the NBD handshake to not reach the point of the TLS negotiation, then waiting for the server to go offline. When the NBD server is stopped, closing the attacker's socket can cause qemu to crash, forming a denial of service attack.

Other sources

A flaw was found in the QEMU NBD Server. This vulnerability allows a denial of service (DoS) attack via improper synchronization during socket closure when a client keeps a socket open as the server is taken offline.

NVD

Qemu: denial of service via improper synchronization in qemu nbd server during socket closure

Microsoft

Affected Software

3 affected componentsFixes available
Qemu Qemu
Microsoft cbl2 qemu 6.2.0-25<6.2.0-26
6.2.0-26
Microsoft azl3 qemu 8.2.0-17<8.2.0-18
8.2.0-18

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 6.2.0-26
  2. Upgrade

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

    Fixed in 8.2.0-18

Event History

Aug 2, 2024
Data Sourced
via Red Hat·11:35 AM
DescriptionSeverityAffected Software
Aug 5, 2024
CVE Published
via MITRE·01:19 PM
Data Sourced
via MITRE·01:19 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityWeakness
Sep 4, 2025
Data Sourced
via Microsoft·11:09 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·11:09 AM
Affected Software
Updated
via Microsoft·11:09 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2024-7409?

The severity of CVE-2024-7409 is classified according to its potential impact on system stability and data integrity during NBD server operations.

2

How do I fix CVE-2024-7409?

To fix CVE-2024-7409, ensure that you are running the latest patched version of QEMU provided by your vendor.

3

What are the risks of not addressing CVE-2024-7409?

Not addressing CVE-2024-7409 can lead to unexpected crashes of qemu while handling NBD server connections, affecting service availability.

4

Which software is affected by CVE-2024-7409?

CVE-2024-7409 affects the QEMU KVM software that uses NBD for storage migration and similar tasks.

5

How does CVE-2024-7409 affect the NBD server?

CVE-2024-7409 can cause the qemu process to crash if a client maintains an open socket when the NBD server is taken offline.

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