System hang via unchecked virtio-pmem device status
Published Nov 8, 2024 · Updated May 11, 2026
Denial of service in affected Linux releases allows local users to hang the system through a bad-status virtio-pmem device. virtio_pmem_flush() sends a flush request without first confirming that the device is activated, then waits indefinitely for a host acknowledgment when the device status is bad. Local low-privileged access and a configured virtio persistent-memory device are required; the observed consequence is a system hang.
Summary
What happened
Denial of service in affected Linux releases allows local users to hang the system through a bad-status virtio-pmem device. virtio_pmem_flush() sends a flush request without first confirming that the device is activated, then waits indefinitely for a host acknowledgment when the device status is bad. Local low-privileged access and a configured virtio persistent-memory device are required; the observed consequence is a system hang.
The record
- CVE
- CVE-2024-50184
- Published
- Nov 8, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-754, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 8, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.3
- Affected versionversion=6e84200c0a2994b991259d19450eee561029bf70 <4ce662fe4be6fbc2595d9ef4888b2b6e778c99ed
- Affected versionversion=6e84200c0a2994b991259d19450eee561029bf70 <59ac565c6277d4be6661e81ea6a7f3ca2c5e4e36
- Affected versionversion=6e84200c0a2994b991259d19450eee561029bf70 <6a5ca0ab94e13a1474bf7ad8437a975c2193618f
- Affected versionversion=6e84200c0a2994b991259d19450eee561029bf70 <9a2bc9b6f929a2ce1ebe4d1a796ddab37568c5b4
- Affected versionversion=6e84200c0a2994b991259d19450eee561029bf70 <b01793cc63dd39c8f12b9a3d8dc115fbebb19e2a
- Affected versionversion=6e84200c0a2994b991259d19450eee561029bf70 <ce7a3a62cc533c922072f328fd2ea2fd7cb893d4
- Affected versionversion=6e84200c0a2994b991259d19450eee561029bf70 <e25fbcd97cf52c3c9824d44b5c56c19673c3dd50
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo