CVE-2024-43880: mlxsw: spectrum_acl_erp: Fix object nesting warning
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.22% (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 0e59c2d22853266704e127915653598f7f104037, 25c6fd9648ad05da493a5d30881896a78a08b624, 36a9996e020dd5aa325e0ecc55eb2328288ea6bb.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0e59c2d22853266704e127915653598f7f104037, 25c6fd9648ad05da493a5d30881896a78a08b624, 36a9996e020dd5aa325e0ecc55eb2328288ea6bb 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_erp: Fix object nesting warning ACLs in Spectrum-2 and newer ASICs can reside in the algorithmic TCAM (A-TCAM) or in the ordinary circuit TCAM (C-TCAM). The former can contain more ACLs (i.e., tc filters), but the number of masks in each region (i.e., tc chain) is limited. In order to mitigate the effects of the above limitation, the device allows filters to share a single mask if their masks only differ in up to 8 consecutive bits. For example, dst_ip/25 can be represented using dst_ip/24 with a delta of 1 bit. The C-TCAM does not have a limit on the number of masks being used (and therefore does not support mask aggregation), but can contain a limited number of filters. The driver uses the "objagg" library to perform the mask aggregation by passing it objects that consist of the filter's mask and whether the filter is to be inserted into the A-TCAM or the C-TCAM since filters in different TCAMs cannot share a mask. The set of created objects is dependent on the insertion order of the filters and is not necessarily optimal. Therefore, the driver will periodically ask the library to compute a more optimal set ("hints") by looking at all the existing objects. When the library asks the driver whether two objects can be aggregated the driver only compares the provided masks and ignores the A-TCAM / C-TCAM indication. This is the right thing to do since the goal is to move as many filters as possible to the A-TCAM. The driver also forbids two identical masks from being aggregated since this can only happen if one was intentionally put in the C-TCAM to avoid a conflict in the A-TCAM. The above can result in the following set of hints: H1: {mask X, A-TCAM} -> H2: {mask Y, A-TCAM} // X is Y + delta H3: {mask Y, C-TCAM} -> H4: {mask Z, A-TCAM} // Y is Z + delta After getting the hints from the library the driver will start migrating filters from one region to another while consulting the computed hints and instructing the device to perform a lookup in both regions during the transition. Assuming a filter with mask X is being migrated into the A-TCAM in the new region, the hints lookup will return H1. Since H2 is the parent of H1, the library will try to find the object associated with it and create it if necessary in which case another hints lookup (recursive) will be performed. This hints lookup for {mask Y, A-TCAM} will either return H2 or H3 since the driver passes the library an object comparison function that ignores the A-TCAM / C-TCAM indication. This can eventually lead to nested objects which are not supported by the library [1]. Fix by removing the object comparison function from both the driver and the library as the driver was the only user. That way the lookup will only return exact matches. I do not have a reliable reproducer that can reproduce the issue in a timely manner, but before the fix the issue would reproduce in several minutes and with the fix it does not reproduce in over an hour. Note that the current usefulness of the hints is limited because they include the C-TCAM indication and represent aggregation that cannot actually happen. This will be addressed in net-next. [1] WARNING: CPU: 0 PID: 153 at lib/objagg.c:170 objagg_obj_parent_assign+0xb5/0xd0 Modules linked in: CPU: 0 PID: 153 Comm: kworker/0:18 Not tainted 6.9.0-rc6-custom-g70fbc2c1c38b #42 Hardware name: Mellanox Technologies Ltd. MSN3700C/VMOD0008, BIOS 5.11 10/10/2018 Workqueue: mlxsw_core mlxsw_sp_acl_tcam_vregion_rehash_work RIP: 0010:objagg_obj_parent_assign+0xb5/0xd0 [...] Call Trace: <TASK> __objagg_obj_get+0x2bb/0x580 objagg_obj_get+0xe/0x80 mlxsw_sp_acl_erp_mask_get+0xb5/0xf0 mlxsw_sp_acl_atcam_entry_add+0xe8/0x3c0 mlxsw_sp_acl_tcam_entry_create+0x5e/0xa0 mlxsw_sp_acl_tcam_vchunk_migrate_one+0x16b/0x270 mlxsw_sp_acl_tcam_vregion_rehash_work+0xbe/0x510 process_one_work+0x151/0x370
- Published
- Aug 20, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-401
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.1 and later · before 5.4.282
- linux linux kernel5.5 and later · before 5.10.224
- linux linux kernel5.11 and later · before 5.15.165
- linux linux kernel5.16 and later · before 6.1.103
- linux linux kernel6.2 and later · before 6.6.44
- linux linux kernel6.7 and later · before 6.10.3
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
- 9069a3817d82b01b3a55da382c774e3575946130 and later · before 4dc09f6f260db3c4565a4ec52ba369393598f2fbaffected · git
- 9069a3817d82b01b3a55da382c774e3575946130 and later · before 36a9996e020dd5aa325e0ecc55eb2328288ea6bbaffected · git
- 9069a3817d82b01b3a55da382c774e3575946130 and later · before 9a5261a984bba4f583d966c550fa72c33ff3714eaffected · git
- 9069a3817d82b01b3a55da382c774e3575946130 and later · before 25c6fd9648ad05da493a5d30881896a78a08b624affected · git
- 9069a3817d82b01b3a55da382c774e3575946130 and later · before 0e59c2d22853266704e127915653598f7f104037affected · git
- 9069a3817d82b01b3a55da382c774e3575946130 and later · before fb5d4fc578e655d113f09565f6f047e15f7ab578affected · git
- 9069a3817d82b01b3a55da382c774e3575946130 and later · before 97d833ceb27dc19f8777d63f90be4a27b5daeedfaffected · git
- before 5.1not affected · semver
- 5.4.282 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.106-1 | 6.1.106-1 |
| Debian:13 | linux | before 6.10.3-1 | 6.10.3-1 |
| Red Hat:rhel_eus:9.4::appstream | bpftool-debuginfo | before 0:7.3.0-427.76.1.el9_4 | 0:7.3.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-devel | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-devel | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-devel-matched | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-devel | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-devel-matched | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-devel | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-devel-matched | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-doc | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-rt-debug-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-rt-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-tools-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
+56
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-43877Aug 20, 2024 · media: pci: ivtv: Add check for DMA map result28Monitor
- ← EarlierCVE-2024-43878Aug 20, 2024 · xfrm: Fix input error path memory access28Monitor
- Later →CVE-2024-43881Aug 20, 2024 · wifi: ath12k: change DMA direction while mapping reinjected packets28Monitor
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 | 0e59c2d22853266704e127915653598f7f104037 | Vendor (CNA) |
| Linux Linux | 25c6fd9648ad05da493a5d30881896a78a08b624 | Vendor (CNA) |
| Linux Linux | 36a9996e020dd5aa325e0ecc55eb2328288ea6bb | Vendor (CNA) |
| Linux Linux | 4dc09f6f260db3c4565a4ec52ba369393598f2fb | Vendor (CNA) |
| Linux Linux | 97d833ceb27dc19f8777d63f90be4a27b5daeedf | Vendor (CNA) |
| Linux Linux | 9a5261a984bba4f583d966c550fa72c33ff3714e | Vendor (CNA) |
| Linux Linux | fb5d4fc578e655d113f09565f6f047e15f7ab578 | Vendor (CNA) |
| debian:linux | 6.1.106-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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-1309 · Aug 21, 2024(Linux Kernel Güvenlik Bildirimi)
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)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS 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 (8 more)Show less
- git.kernel.org/stable/c/25c6fd9648ad05da493a5d30881896a78a08b624
- git.kernel.org/stable/c/36a9996e020dd5aa325e0ecc55eb2328288ea6bb
- git.kernel.org/stable/c/4dc09f6f260db3c4565a4ec52ba369393598f2fb
- git.kernel.org/stable/c/97d833ceb27dc19f8777d63f90be4a27b5daeedf
- git.kernel.org/stable/c/9a5261a984bba4f583d966c550fa72c33ff3714e
- git.kernel.org/stable/c/fb5d4fc578e655d113f09565f6f047e15f7ab578
- lists.debian.org/debian-lts-announce/2024/10/msg00003.html
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.