medium
5.5
CWE
755
Advisory Published
Updated

CVE-2024-50001: net/mlx5: Fix error path in multi-packet WQE transmit

First published: Mon Oct 21 2024(Updated: )

In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix error path in multi-packet WQE transmit Remove the erroneous unmap in case no DMA mapping was established The multi-packet WQE transmit code attempts to obtain a DMA mapping for the skb. This could fail, e.g. under memory pressure, when the IOMMU driver just can't allocate more memory for page tables. While the code tries to handle this in the path below the err_unmap label it erroneously unmaps one entry from the sq's FIFO list of active mappings. Since the current map attempt failed this unmap is removing some random DMA mapping that might still be required. If the PCI function now presents that IOVA, the IOMMU may assumes a rogue DMA access and e.g. on s390 puts the PCI function in error state. The erroneous behavior was seen in a stress-test environment that created memory pressure.

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel>=5.10<5.10.227
Linux Kernel>=5.11<5.15.168
Linux Kernel>=5.16<6.1.113
Linux Kernel>=6.2<6.6.55
Linux Kernel>=6.7<6.10.14
Linux Kernel>=6.11<6.11.3
Linux Kernel=6.12-rc1
debian/linux<=5.10.223-1
5.10.234-1
6.1.129-1
6.1.128-1
6.12.20-1
6.12.21-1
debian/linux-6.1
6.1.129-1~deb11u1

Remedy

https://git.kernel.org/stable/c/26fad69b34fcba80d5c7d9e651f628e6ac927754

Remedy

https://git.kernel.org/stable/c/2bcae12c795f32ddfbf8c80d1b5f1d3286341c32

Remedy

https://git.kernel.org/stable/c/8bb8c12fb5e2b1f03d603d493c92941676f109b5

Remedy

https://git.kernel.org/stable/c/ca36d6c1a49b6965c86dd528a73f38bc62d9c625

Remedy

https://git.kernel.org/stable/c/ce828b347cf1b3c1b12b091d02463c35ce5097f5

Remedy

https://git.kernel.org/stable/c/ecf310aaf256acbc8182189fe0aa1021c3ddef72

Remedy

https://git.kernel.org/stable/c/fc357e78176945ca7bcacf92ab794b9ccd41b4f4

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2024-50001?

    CVE-2024-50001 has been classified with a severity rating that indicates it poses a risk to affected systems, particularly in the Linux kernel.

  • How do I fix CVE-2024-50001?

    To remediate CVE-2024-50001, users should apply the latest patches or updates provided for the affected versions of the Linux kernel.

  • Which Linux kernel versions are affected by CVE-2024-50001?

    CVE-2024-50001 affects multiple versions of the Linux kernel ranging from 5.10 to 6.12-rc1.

  • What systems are impacted by CVE-2024-50001?

    Systems running the specified vulnerable Linux kernel versions are impacted by CVE-2024-50001.

  • Is there a workaround for CVE-2024-50001?

    While applying official patches is recommended, temporary workarounds may involve disabling certain kernel features related to multi-packet WQE transmit.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203