Loading vulnerability…
A memory leak vulnerability existed in the Linux kernel mlxsw Spectrum ACL TCAM rehash logic. The flaw was in the handling of delayed rehash work in the spectrum_acl_tcam path during ACL region migration and dismantle. The implementation assumed that a non-negative credit count at the end of the work indicated migration completion, and used that assumption to decide whether work would remain pending. After changes made to address a prior use-after-free condition, that assumption was no longer valid: a non-negative credit count could also occur when the work encountered an error and would later resume. In that state, delayed work could remain pending while still holding allocated rehash hints created at migration start. If the ACL region was then dismantled and the pending work canceled, the associated hints were not freed, resulting in a kernel memory leak. The fix frees hints when they are associated with work canceled while still pending.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux mlxsw Spectrum ACL TCAM memory-leak vulnerability when rehash work is cancelled.
A memory leak in the Linux kernel mlxsw Spectrum ACL TCAM driver when canceling rehash work.
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.