CVE-2024-26586: mlxsw: spectrum_acl_tcam: Fix stack corruption
Noroxi assessment
Priority: Monitor (action score 26/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.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2f5e1565740490706332c06f36211d4ce0f88e62, 348112522a35527c5bcba933b9fefb40a4f44f15, 483ae90d8f976f8339cf81066312e1329f2d3706.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2f5e1565740490706332c06f36211d4ce0f88e62, 348112522a35527c5bcba933b9fefb40a4f44f15, 483ae90d8f976f8339cf81066312e1329f2d3706 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 stack corruption When tc filters are first added to a net device, the corresponding local port gets bound to an ACL group in the device. The group contains a list of ACLs. In turn, each ACL points to a different TCAM region where the filters are stored. During forwarding, the ACLs are sequentially evaluated until a match is found. One reason to place filters in different regions is when they are added with decreasing priorities and in an alternating order so that two consecutive filters can never fit in the same region because of their key usage. In Spectrum-2 and newer ASICs the firmware started to report that the maximum number of ACLs in a group is more than 16, but the layout of the register that configures ACL groups (PAGT) was not updated to account for that. It is therefore possible to hit stack corruption [1] in the rare case where more than 16 ACLs in a group are required. Fix by limiting the maximum ACL group size to the minimum between what the firmware reports and the maximum ACLs that fit in the PAGT register. Add a test case to make sure the machine does not crash when this condition is hit. [1] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: mlxsw_sp_acl_tcam_group_update+0x116/0x120 [...] dump_stack_lvl+0x36/0x50 panic+0x305/0x330 __stack_chk_fail+0x15/0x20 mlxsw_sp_acl_tcam_group_update+0x116/0x120 mlxsw_sp_acl_tcam_group_region_attach+0x69/0x110 mlxsw_sp_acl_tcam_vchunk_get+0x492/0xa20 mlxsw_sp_acl_tcam_ventry_add+0x25/0xe0 mlxsw_sp_acl_rule_add+0x47/0x240 mlxsw_sp_flower_replace+0x1a9/0x1d0 tc_setup_cb_add+0xdc/0x1c0 fl_hw_replace_filter+0x146/0x1f0 fl_change+0xc17/0x1360 tc_new_tfilter+0x472/0xb90 rtnetlink_rcv_msg+0x313/0x3b0 netlink_rcv_skb+0x58/0x100 netlink_unicast+0x244/0x390 netlink_sendmsg+0x1e4/0x440 ____sys_sendmsg+0x164/0x260 ___sys_sendmsg+0x9a/0xe0 __sys_sendmsg+0x7a/0xc0 do_syscall_64+0x40/0xe0 entry_SYSCALL_64_after_hwframe+0x63/0x6b
- Published
- Feb 22, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-787
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.7 / 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
- 6.7
- CNA · Linux
- 7.8
- 1.1 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.19.0 and later · before 5.10.209
- linux linux kernel5.11.0 and later · before 5.15.148
- linux linux kernel5.16.0 and later · before 6.1.79
- linux linux kernel6.2.0 and later · before 6.6.14
- linux linux kernel6.7.0 and later · before 6.7.2
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
- 4.19affected
- c3ab435466d5109b2c7525a3b90107d4d9e918fc and later · before 56750ea5d15426b5f307554e7699e8b5f76c3182affected · git
- c3ab435466d5109b2c7525a3b90107d4d9e918fc and later · before 348112522a35527c5bcba933b9fefb40a4f44f15affected · git
- c3ab435466d5109b2c7525a3b90107d4d9e918fc and later · before 6fd24675188d354b1cad47462969afa2ab09d819affected · git
- c3ab435466d5109b2c7525a3b90107d4d9e918fc and later · before 2f5e1565740490706332c06f36211d4ce0f88e62affected · git
- c3ab435466d5109b2c7525a3b90107d4d9e918fc and later · before a361c2c1da5dbb13ca67601cf961ab3ad68af383affected · git
- c3ab435466d5109b2c7525a3b90107d4d9e918fc and later · before 483ae90d8f976f8339cf81066312e1329f2d3706affected · git
- before 4.19not affected · semver
- 5.10.209 and later · up to and including 5.10.*not affected · semver
- 5.15.148 and later · up to and including 5.15.*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.82-1 | 6.1.82-1 |
| Debian:13 | linux | before 6.6.15-1 | 6.6.15-1 |
| Red Hat:rhel_aus:8.2::baseos | bpftool | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | bpftool-debuginfo | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-abi-whitelists | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-core | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debug | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debug-core | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debug-debuginfo | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debug-devel | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debug-modules | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debug-modules-extra | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debuginfo | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-debuginfo-common-x86_64 | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-devel | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-doc | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-modules | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-modules-extra | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-tools | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-tools-debuginfo | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-tools-libs | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | perf | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | perf-debuginfo | before 0:4.18.0-193.133.1.el8_2 | 0:4.18.0-193.133.1.el8_2 |
+96
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-2023-52450Feb 22, 2024 · perf/x86/intel/uncore: Fix NULL pointer dereference issue in upi_fill_topology()22Monitor
- ← EarlierCVE-2023-52451Feb 22, 2024 · powerpc/pseries/memhp: Fix access beyond end of drmem array31Monitor
- Later →CVE-2024-26587Feb 22, 2024 · net: netdevsim: don't try to destroy PHC on VFs22Monitor
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 | 2f5e1565740490706332c06f36211d4ce0f88e62 | Vendor (CNA) |
| Linux Linux | 348112522a35527c5bcba933b9fefb40a4f44f15 | Vendor (CNA) |
| Linux Linux | 483ae90d8f976f8339cf81066312e1329f2d3706 | Vendor (CNA) |
| Linux Linux | 56750ea5d15426b5f307554e7699e8b5f76c3182 | Vendor (CNA) |
| Linux Linux | 6fd24675188d354b1cad47462969afa2ab09d819 | Vendor (CNA) |
| Linux Linux | a361c2c1da5dbb13ca67601cf961ab3ad68af383 | Vendor (CNA) |
| almalinux:bpftool | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.82-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.62.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.62.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.62.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.62.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.62.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.62.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.62.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.62.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.62.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.62.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.62.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
+1
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0126 · Feb 23, 2024(Linux Kernel Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 (6 more)Show less
- git.kernel.org/stable/c/348112522a35527c5bcba933b9fefb40a4f44f15
- git.kernel.org/stable/c/483ae90d8f976f8339cf81066312e1329f2d3706
- git.kernel.org/stable/c/56750ea5d15426b5f307554e7699e8b5f76c3182
- git.kernel.org/stable/c/6fd24675188d354b1cad47462969afa2ab09d819
- git.kernel.org/stable/c/a361c2c1da5dbb13ca67601cf961ab3ad68af383
- lists.debian.org/debian-lts-announce/2024/06/msg00016.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.