CVE-2026-10673 is an out-of-bounds write vulnerability in the Zephyr RTOS ADIN2111/ADIN1110 10BASE-T1S/T1L Ethernet driver affecting releases 3.7.0 through 4.4.0. In OPEN Alliance SPI mode, the driver function eth_adin2111_oa_data_read() reassembles received Ethernet frames by copying device-supplied 64-byte chunks into a fixed static receive buffer, ctx->buf, sized by CONFIG_ETH_ADIN2111_BUFFER_SIZE, which defaults to 1524 bytes. The write cursor is advanced for each valid chunk, but the vulnerable code did not verify that the cumulative write position plus chunk length remained within the destination buffer. Because both the number of chunks and the per-chunk length are derived from received frame data, an attacker on the attached single-pair Ethernet segment can transmit an oversized frame that causes attacker-controlled bytes to be written past the end of the static buffer into adjacent driver or kernel memory. The cursor is only reset on a start-of-frame chunk, which contributes to the unsafe reassembly behavior. The flaw was introduced when OA SPI support was added and was corrected by adding a bounds check that drops oversized frames and resets the cursor before copying.
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.
3 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.