Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-35852: mlxsw: spectrum_acl_tcam: Fix memory leak when canceling rehash work

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.25% (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 51cefc9da400b953fee749c9e5d26cd4a2b5d758, 5bfe7bf9656ed2633718388f12b7c38b86414a04, 63d814d93c5cce4c18284adc810028f28dca493f; Azure Linux 3.0 ARM 6.6.35.1-1; Azure Linux 3.0 x64 6.6.35.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 51cefc9da400b953fee749c9e5d26cd4a2b5d758, 5bfe7bf9656ed2633718388f12b7c38b86414a04, 63d814d93c5cce4c18284adc810028f28dca493f; Azure Linux 3.0 ARM 6.6.35.1-1; Azure Linux 3.0 x64 6.6.35.1-1 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 memory leak when canceling rehash work The rehash delayed work is rescheduled with a delay if the number of credits at end of the work is not negative as supposedly it means that the migration ended. Otherwise, it is rescheduled immediately. After "mlxsw: spectrum_acl_tcam: Fix possible use-after-free during rehash" the above is no longer accurate as a non-negative number of credits is no longer indicative of the migration being done. It can also happen if the work encountered an error in which case the migration will resume the next time the work is scheduled. The significance of the above is that it is possible for the work to be pending and associated with hints that were allocated when the migration started. This leads to the hints being leaked [1] when the work is canceled while pending as part of ACL region dismantle. Fix by freeing the hints if hints are associated with a work that was canceled while pending. Blame the original commit since the reliance on not having a pending work associated with hints is fragile. [1] unreferenced object 0xffff88810e7c3000 (size 256): comm "kworker/0:16", pid 176, jiffies 4295460353 hex dump (first 32 bytes): 00 30 95 11 81 88 ff ff 61 00 00 00 00 00 00 80 .0......a....... 00 00 61 00 40 00 00 00 00 00 00 00 04 00 00 00 ..a.@........... backtrace (crc 2544ddb9): [<00000000cf8cfab3>] kmalloc_trace+0x23f/0x2a0 [<000000004d9a1ad9>] objagg_hints_get+0x42/0x390 [<000000000b143cf3>] mlxsw_sp_acl_erp_rehash_hints_get+0xca/0x400 [<0000000059bdb60a>] mlxsw_sp_acl_tcam_vregion_rehash_work+0x868/0x1160 [<00000000e81fd734>] process_one_work+0x59c/0xf20 [<00000000ceee9e81>] worker_thread+0x799/0x12c0 [<00000000bda6fe39>] kthread+0x246/0x300 [<0000000070056d23>] ret_from_fork+0x34/0x70 [<00000000dea2b93e>] ret_from_fork_asm+0x1a/0x30

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 17, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 17th percentile

Report tools

JSON

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.

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.

Follow CVE-2024-35852

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux 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.275
  • 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 kernel6.2 and later · before 6.6.30
  • linux linux kernel6.7 and later · before 6.8.9
  • 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
    • c9c9af91f1d9a636aecc55302c792538e549a430 and later · before 51cefc9da400b953fee749c9e5d26cd4a2b5d758affected · git
    • c9c9af91f1d9a636aecc55302c792538e549a430 and later · before 857ed800133ffcfcee28582090b63b0cbb8ba59daffected · git
    • c9c9af91f1d9a636aecc55302c792538e549a430 and later · before 63d814d93c5cce4c18284adc810028f28dca493faffected · git
    • c9c9af91f1d9a636aecc55302c792538e549a430 and later · before 5bfe7bf9656ed2633718388f12b7c38b86414a04affected · git
    • c9c9af91f1d9a636aecc55302c792538e549a430 and later · before de1aaefa75be9d0ec19c9a3e0e2f9696de20c6abaffected · git
    • c9c9af91f1d9a636aecc55302c792538e549a430 and later · before d72dd6fcd7886d0523afbab8b4a4b22d17addd7daffected · git
    • c9c9af91f1d9a636aecc55302c792538e549a430 and later · before fb4e2b70a7194b209fc7320bbf33b375f7114bd5affected · 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.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.90-16.1.90-1
Debian:13linuxbefore 6.8.9-16.8.9-1
Red Hat:rhel_aus:8.6::baseosbpftoolbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseosbpftool-debuginfobefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernelbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-abi-stablelistsbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-corebefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debugbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-corebefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-debuginfobefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-develbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-modulesbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-modules-extrabefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debuginfobefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-develbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-docbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-modulesbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-modules-extrabefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-toolsbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-tools-debuginfobefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-tools-libsbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseosperfbefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6
Red Hat:rhel_aus:8.6::baseosperf-debuginfobefore 0:4.18.0-372.118.1.el8_60:4.18.0-372.118.1.el8_6

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-35850May 17, 2024 · Bluetooth: qca: fix NULL-deref on non-serdev setup
    22Monitor
  • ← EarlierCVE-2024-35851May 17, 2024 · Bluetooth: qca: fix NULL-deref on non-serdev suspend
    22Monitor
  • Later →CVE-2024-35853May 17, 2024 · mlxsw: spectrum_acl_tcam: Fix memory leak during rehash
    25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux51cefc9da400b953fee749c9e5d26cd4a2b5d758Vendor (CNA)
Linux Linux5bfe7bf9656ed2633718388f12b7c38b86414a04Vendor (CNA)
Linux Linux63d814d93c5cce4c18284adc810028f28dca493fVendor (CNA)
Linux Linux857ed800133ffcfcee28582090b63b0cbb8ba59dVendor (CNA)
Linux Linuxd72dd6fcd7886d0523afbab8b4a4b22d17addd7dVendor (CNA)
Linux Linuxde1aaefa75be9d0ec19c9a3e0e2f9696de20c6abVendor (CNA)
Linux Linuxfb4e2b70a7194b209fc7320bbf33b375f7114bd5Vendor (CNA)
Azure Linux 3.0 ARM6.6.35.1-1 · hyperv-daemonsMicrosoft (MSRC)
Azure Linux 3.0 x646.6.35.1-1 · hyperv-daemonsMicrosoft (MSRC)
debian:linux6.1.90-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-477.67.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-477.67.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-477.67.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-477.67.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-477.67.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-477.67.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-477.67.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-477.67.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-477.67.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-477.67.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-477.67.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-477.67.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage 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.

Finders, 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.

All national notices →

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

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records