CVE-2024-41073: nvme: avoid double free special payload

Published Jul 29, 2024
·
Updated

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

nvme: avoid double free special payload

If a discard request needs to be retried, and that retry may fail before a new special payload is added, a double free will result. Clear the RQFSPECIALLOAD when the request is cleaned.

Other sources

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

nvme: avoid double free special payload

The Linux kernel CVE team has assigned CVE-2024-41073 to this issue.

Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024072909-CVE-2024-41073-1fb9@gregkh/T

— Red Hat

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

19 affected componentsFixes available
debian/linux<=5.10.223-1, <=5.10.234-1
6.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Linux Linux kernel<5.15.164
Linux Linux kernel>=5.16<6.1.101
Linux Linux kernel>=6.2<6.6.42
Linux Linux kernel>=6.7<6.9.11
IBM QRadar<=7.5.0 - 7.5.0 UP15 IF02
redhat/kernel<5.15.164
5.15.164
redhat/kernel<6.1.101
6.1.101
redhat/kernel<6.6.42
6.6.42
redhat/kernel<6.9.11
6.9.11
redhat/kernel<6.10
6.10
Debian Debian Linux=11.0
Linux Linux kernel>=4.10<5.10.237
Linux Linux kernel>=5.11<5.15.164
Microsoft azl3 kernel 6.6.35.1-5<6.6.47.1-1
6.6.47.1-1
Microsoft cbl2 kernel 5.15.164.1-1<5.15.164.1-1
5.15.164.1-1
Microsoft cbl2 kernel 5.15.162.2-1<5.15.164.1-1
5.15.164.1-1
Microsoft azl3 kernel 6.6.47.1-1<6.6.47.1-1
6.6.47.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.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 redhat/kernel to a version that resolves this vulnerability.

    Fixed in 5.15.164
  4. Upgrade

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

    Fixed in 6.1.101
  5. Upgrade

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

    Fixed in 6.6.42
  6. Upgrade

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

    Fixed in 6.9.11
  7. Upgrade

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

    Fixed in 6.10
  8. Upgrade

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

    Fixed in 6.6.47.1-1
  9. Upgrade

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

    Fixed in 5.15.164.1-1

Event History

Jul 29, 2024
CVE Published
via MITRE·02:57 PM
Data Sourced
via MITRE·02:57 PM
DescriptionSeverity
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 30, 2024
Data Sourced
via Red Hat·01:45 PM
DescriptionSeverityAffected Software
Sep 11, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Oct 23, 2024
Data Sourced
via Launchpad·11:27 PM
Description
May 1, 2025
Data Sourced
via Ubuntu·12:33 AM
RemedyDescriptionSeverityAffected Software
May 25, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Jan 2, 58561
Event
via MITRE·10:47 PM

Parent advisories

This vulnerability appears in the following advisories.

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-41073?

CVE-2024-41073 has been classified as a medium severity vulnerability due to the potential for a double free condition.

2

How do I fix CVE-2024-41073?

To resolve CVE-2024-41073, update your Linux kernel to versions 5.15.164, 6.1.101, 6.6.42, 6.9.11, or 6.10 as applicable.

3

What systems are affected by CVE-2024-41073?

CVE-2024-41073 affects various versions of the Linux kernel, specifically those below 5.15.164 and versions within specified ranges.

4

Is there a workaround for CVE-2024-41073?

Currently, there are no documented workarounds for CVE-2024-41073 other than applying the recommended updates.

5

Can CVE-2024-41073 lead to data loss?

Yes, CVE-2024-41073 could potentially lead to data loss due to mishandling of discard requests.

Company

Resources

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