CVE-2026-64122 is a use-after-free vulnerability in the Linux kernel mlx5e networking driver. The flaw is in mlx5e_tx_reporter_timeout_recover(), which accesses sq->netdev after mlx5e_safe_reopen_channels() has already torn down and freed the channel object and its embedded send queues. This leaves stale references reachable during the timeout recovery path. The fix replaces unsafe references to sq->netdev with priv->netdev, which remains valid across channel teardown. The bug was demonstrated by a KASAN-reported invalid read in the recovery path within the mlx5_core module.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.