CVE-2024-36007: mlxsw: spectrum_acl_tcam: Fix warning during rehash
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 039992b6d2df097c65f480dcf269de3d2656f573, 0b88631855026b55cad901ac28d081e0f358e596, 17e9e0bbae652b9b2049e51699e93dfa60b2988d.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 039992b6d2df097c65f480dcf269de3d2656f573, 0b88631855026b55cad901ac28d081e0f358e596, 17e9e0bbae652b9b2049e51699e93dfa60b2988d or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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>
- Published
- May 20, 2024
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- linux linux kernel5.5 and later · before 5.10.216
- linux linux kernel5.11 and later · before 5.15.158
- linux linux kernel5.16 and later · before 6.1.90
- linux linux kernel5.1 and later · before 5.4.275
- linux linux kernel6.7 and later · before 6.8.9
- linux linux kernel6.2 and later · before 6.6.30
- linux linux kernel6.9
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.1affected
- 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf and later · before 0b88631855026b55cad901ac28d081e0f358e596affected · git
- 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf and later · before 1d76bd2a0034d0d08045c1c6adf2235d88982952affected · git
- 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf and later · before 039992b6d2df097c65f480dcf269de3d2656f573affected · git
- 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf and later · before 751d352858108314efd33dddd5a9a2b6bf7d6916affected · git
- 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf and later · before e890456051fe8c57944b911defb3e6de91315861affected · git
- 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf and later · before 17e9e0bbae652b9b2049e51699e93dfa60b2988daffected · git
- 6f9579d4e3021b17b0a4cde6b04a6c94c9575cdf and later · before 743edc8547a92b6192aa1f1b6bb78233fa21dc9baffected · git
- before 5.1not affected · semver
- 5.4.275 and later · up to and including 5.4.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.90-1 | 6.1.90-1 |
| Debian:13 | linux | before 6.8.9-1 | 6.8.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-36005May 20, 2024 · netfilter: nf_tables: honor table dormant flag from netdev release event path22Monitor
- ← EarlierCVE-2024-36006May 20, 2024 · mlxsw: spectrum_acl_tcam: Fix incorrect list API usage22Monitor
- Later →CVE-2024-36008May 20, 2024 · ipv4: check for NULL idev in ip_route_use_hint()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 039992b6d2df097c65f480dcf269de3d2656f573 | Vendor (CNA) |
| Linux Linux | 0b88631855026b55cad901ac28d081e0f358e596 | Vendor (CNA) |
| Linux Linux | 17e9e0bbae652b9b2049e51699e93dfa60b2988d | Vendor (CNA) |
| Linux Linux | 1d76bd2a0034d0d08045c1c6adf2235d88982952 | Vendor (CNA) |
| Linux Linux | 743edc8547a92b6192aa1f1b6bb78233fa21dc9b | Vendor (CNA) |
| Linux Linux | 751d352858108314efd33dddd5a9a2b6bf7d6916 | Vendor (CNA) |
| Linux Linux | e890456051fe8c57944b911defb3e6de91315861 | Vendor (CNA) |
| debian:linux | 6.1.90-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/0b88631855026b55cad901ac28d081e0f358e596
- git.kernel.org/stable/c/17e9e0bbae652b9b2049e51699e93dfa60b2988d
- git.kernel.org/stable/c/1d76bd2a0034d0d08045c1c6adf2235d88982952
- git.kernel.org/stable/c/743edc8547a92b6192aa1f1b6bb78233fa21dc9b
- git.kernel.org/stable/c/751d352858108314efd33dddd5a9a2b6bf7d6916
- git.kernel.org/stable/c/e890456051fe8c57944b911defb3e6de91315861
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
- cert-portal.siemens.com/productcert/html/ssa-613116.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.