CVE-2024-50184: virtio_pmem: Check device status before requesting flush

Published Nov 8, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

virtiopmem: Check device status before requesting flush

If a pmem device is in a bad status, the driver side could wait for host ack forever in virtiopmemflush(), causing the system to hang.

So add a status check in the beginning of virtiopmemflush() to return early if the device is not activated.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

10 affected componentsFixes available
Linux Linux kernel>=5.3<5.4.285
Linux Linux kernel>=5.5<5.10.227
Linux Linux kernel>=5.11<5.15.168
Linux Linux kernel>=5.16<6.1.113
Linux Linux kernel>=6.2<6.6.57
Linux Linux kernel>=6.7<6.11.4
debian/linux<=5.10.223-1
5.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Microsoft cbl2 kernel 5.15.167.1-2<5.15.173.1-1
5.15.173.1-1
Microsoft cbl2 kernel 5.15.173.1-1<5.15.173.1-1
5.15.173.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 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  2. Upgrade

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

    Fixed in 6.1.129-1~deb11u1
  3. Upgrade

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

    Fixed in 5.15.173.1-1
  4. Configuration

    Apply the fix to virtio_pmem: add a device status check at the beginning of virtio_pmem_flush() to return early if the pmem device is not activated. This prevents waiting for host ack forever when the device is in a bad status.

    Linux kernel virtio_pmem driver virtio_pmem_flush() device status check = return early when device is not activated

Event History

Nov 8, 2024
CVE Published
via MITRE·05:38 AM
Data Sourced
via MITRE·05:38 AM
Description
Data Sourced
via NVD·06:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Dec 13, 2024
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
Severity
Updated
via Microsoft·08:00 AM
SeverityAffected Software
Updated
via Microsoft·08:00 AM
Description
Feb 12, 2025
Data Sourced
via Launchpad·05:18 AM
Description
Apr 29, 2025
Data Sourced
via Ubuntu·06:31 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-50184?

CVE-2024-50184 is considered a high-severity vulnerability due to its potential to cause system hangs.

2

How do I fix CVE-2024-50184?

To fix CVE-2024-50184, update to the latest kernel versions that include the patch, such as 6.1.123-1 or 6.12.11-1.

3

Which Linux kernel versions are affected by CVE-2024-50184?

CVE-2024-50184 affects Linux kernel versions from 5.3 to below 5.4.285, and versions below 6.2.

4

How does CVE-2024-50184 impact system performance?

CVE-2024-50184 can cause significant performance issues by causing the system to hang indefinitely during flush operations.

5

Is CVE-2024-50184 specific to certain distributions?

Yes, CVE-2024-50184 specifically affects Debian-based systems using the vulnerable kernel versions.

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