Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-35852, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.26% · top 83% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected c9c9af91f1d9a636aecc55302c792538e549a430 – < 51cefc9da400b953fee749c9e5d26cd4a2b5d758
    • affected c9c9af91f1d9a636aecc55302c792538e549a430 – < 857ed800133ffcfcee28582090b63b0cbb8ba59d
    • affected c9c9af91f1d9a636aecc55302c792538e549a430 – < 63d814d93c5cce4c18284adc810028f28dca493f
    • affected c9c9af91f1d9a636aecc55302c792538e549a430 – < 5bfe7bf9656ed2633718388f12b7c38b86414a04
    • affected c9c9af91f1d9a636aecc55302c792538e549a430 – < de1aaefa75be9d0ec19c9a3e0e2f9696de20c6ab
    • affected c9c9af91f1d9a636aecc55302c792538e549a430 – < d72dd6fcd7886d0523afbab8b4a4b22d17addd7d
    • affected c9c9af91f1d9a636aecc55302c792538e549a430 – < fb4e2b70a7194b209fc7320bbf33b375f7114bd5
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 5.4.275 – ≤ 5.4.*
    • unaffected 5.10.216 – ≤ 5.10.*
    • unaffected 5.15.158 – ≤ 5.15.*
    • unaffected 6.1.90 – ≤ 6.1.*
    • unaffected 6.6.30 – ≤ 6.6.*
    • unaffected 6.8.9 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-35852 badge
[![CVE-2024-35852](https://cveledger.app/badge/CVE-2024-35852.svg)](https://cveledger.app/cve/CVE-2024-35852)

Record last updated .