Loading vulnerability…
CVE-2023-52667 is a double-free vulnerability in the Linux kernel net/mlx5e driver’s fs_any_create_groups() error-handling path. When kcalloc() successfully allocates ft->g but a subsequent kvzalloc() allocation fails, fs_any_create_groups() frees ft->g. Its caller, fs_any_create_table(), can subsequently invoke mlx5e_destroy_flow_table(), which frees the same allocation again. The fix clears ft->g after the first free so subsequent cleanup does not release it twice.
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.
18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel net/mlx5e double-free vulnerability in fs_any_create_groups(). It affects Google sys-kernel/lakitu-kernel-6_1 versions before 18244.1.7 and could result in high-impact local compromise of confidentiality, integrity, and availability.
Potential double-free in the Linux kernel mlx5e fs_any_create_groups function.
Potential double-free vulnerability in the Linux kernel mlx5e networking driver.
A potential double-free flaw in the Linux kernel mlx5e driver.
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.