Loading vulnerability…
CVE-2024-38586 is a flaw in the Linux kernel r8169 network driver transmit path affecting RTL8125b hardware. When transmitting small fragmented packets, packet padding applied by rtl8169_tso_csum_v2() can change nr_frags after rtl8169_start_xmit() has already inspected it. This stale fragment count can cause invalid entries to be inserted into the transmit ring buffer and subsequently cause dma_unmap_single() to be invoked with a null address. The upstream fix postpones inspection of nr_frags until after padding is applied.
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.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A possible Linux kernel r8169 network-driver ring-buffer corruption issue when handling fragmented transmit packets.
Linux kernel Realtek r8169 driver ring-buffer corruption on fragmented transmit packets.
Possible Linux kernel r8169 network-driver ring-buffer corruption vulnerability when transmitting fragmented packets.
Possible ring-buffer corruption in the Linux kernel r8169 network driver when transmitting fragmented packets.
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.