Loading vulnerability…
CVE-2025-68301 is an out-of-bounds write vulnerability in the Linux kernel atlantic Ethernet driver receive path. While processing large multi-descriptor packets, the driver can accumulate more than MAX_SKB_FRAGS (17) fragments without validating the total fragment count before adding a receive fragment. The fragment index can then exceed the socket-buffer fragment-array bounds in skb_add_rx_frag_netmem(). The corrective change accounts for an additional fragment when the receive buffer length exceeds the configured RX header size and applies the existing fragment-limit check earlier in the receive path.
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.
26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel net atlantic vulnerability involving fragment overflow handling in the RX path.
A Linux kernel net/atlantic vulnerability involving fragment overflow handling in the RX path.
A Linux kernel net/atlantic vulnerability involving fragment overflow handling in the RX path.
A Linux kernel net/atlantic driver flaw in receive-path fragment overflow handling.
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.