CVE-2024-35853 is a memory leak in the Linux kernel mlxsw Spectrum ACL TCAM rehash workflow. During delayed rehash work, filters are migrated between regions through virtual chunks that maintain both an active chunk and a backup chunk. If migration fails, the code attempts a rollback. A failure of that rollback could trigger an additional migration attempt, violating an assumption that no backup chunk exists when the active chunk does not refer to the target region. The backup-chunk reference can consequently be overwritten without releasing its prior allocation, leaking memory. The upstream correction prevents rollback of an already failed rollback and adds a warning to detect invalid future states.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A memory leak during rehashing in the Linux kernel mlxsw Spectrum ACL TCAM driver.
A memory-leak flaw in the Linux kernel mlxsw Spectrum ACL TCAM rehash operation.
Linux kernel mlxsw Spectrum ACL TCAM rehash memory-leak vulnerability.
Linux kernel mlxsw Spectrum ACL TCAM memory leak during rehashing.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.