Loading vulnerability…
A flaw in the Linux kernel r8169 network driver can corrupt the transmit ring buffer when handling small fragmented transmit packets on RTL8125b hardware. The issue occurs because rtl8169_start_xmit() inspects the packet fragment count before padding logic in rtl8169_tso_csum_v2() may modify nr_frags to accommodate hardware quirks. This stale fragment accounting can cause invalid descriptors to be inserted into the transmit ring, eventually triggering dma_unmap_single() on a null address. The vulnerability is therefore rooted in incorrect state handling during transmit descriptor preparation, leading to ring corruption and invalid DMA unmapping operations in kernel space.
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.
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.
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.