Loading vulnerability…
CVE-2024-41066 is a memory-leak vulnerability in the Linux kernel IBM Virtual NIC (ibmvnic) driver's transmit path. The driver validates that a free_map entry identifies a valid transmit-buffer index, but prior to the fix it did not verify that the corresponding tx_buff entry had a null skb pointer. If free_map and tx_buff become unsynchronized, transmission can overwrite an existing skb reference, leaking the old socket buffer. The patch verifies that the destination skb pointer is null before assignment; if it is already populated, the driver warns and frees the stale skb.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel IBM Virtual NIC driver flaw that can leak socket buffers due to missing transmit checks.
A Linux kernel ibmvnic driver vulnerability that could result in an skb leak without transmit-path validation.
A Linux kernel ibmvnic driver vulnerability that can lead to an skb leak without the added transmit check.
Linux kernel ibmvnic transmit-path socket-buffer leak.
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.