Red Hat Enterprise Linux 8: Improper Synchronization
CVE-2024-7409 is a high-severity improper synchronization vulnerability in Red Hat Enterprise Linux 8 from Red Hat, with a CVSS 3.0 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 1.03% chance of exploitation within 30 days, higher than 64% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Red Hat Enterprise Linux 8 you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (redhat.com).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Synchronization
The product utilizes multiple threads, processes, components, or systems to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes.
How developers prevent this class of flaw
- Use industry standard APIs to synchronize your code.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
- access.redhat.com/errata/RHSA-2024:10518
- access.redhat.com/errata/RHSA-2024:10528
- access.redhat.com/errata/RHSA-2024:10813
- access.redhat.com/errata/RHSA-2024:6811
- access.redhat.com/errata/RHSA-2024:6818
- access.redhat.com/errata/RHSA-2024:6964
- access.redhat.com/errata/RHSA-2024:7408
- access.redhat.com/errata/RHSA-2024:8991
- access.redhat.com/errata/RHSA-2024:9136
- access.redhat.com/errata/RHSA-2024:9620
- access.redhat.com/errata/RHSA-2024:9912
- access.redhat.com/security/cve/CVE-2024-7409
- bugzilla.redhat.com/show_bug.cgi?id=2302487
- lists.debian.org/debian-lts-announce/2025/09/msg00011.html
- security.netapp.com/advisory/ntap-20250502-0008/
Other vulnerabilities in Red Hat Enterprise Linux 8
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.9 High severity
- 7.3 High severity
- 7.5 High severity
Recent Improper Synchronization vulnerabilities
- 9.1 Critical severity
- 7.0 High severity
- 8.7 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.