Skip to content
Systems

CVE-2026-10673

8.3
High
EPSS 0.39%Patch availableJul 16, 2026

OOB write in Zephyr ADIN2111/ADIN1110 Ethernet driver allows memory corruption.

common questions

Is CVE-2026-10673 being exploited?

Not confirmed. CVE-2026-10673 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.

How severe is CVE-2026-10673?

CVE-2026-10673 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-10673?

Yes. A fix has been recorded for CVE-2026-10673. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-10673 affect?

CVE-2026-10673 affects Zephyr RTOS v3.7.0 - v4.4.0, drivers/ethernet/eth_adin2111.c, ADIN2111/ADIN1110 single-pair Ethernet devices, Devices using OA SPI (10BASE-T1S/T1L). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-10673?

Upgrade Zephyr to a release containing the fix or apply vendor patch; block OA SPI frames if feasible.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Zephyr RTOS v3.7.0 - v4.4.0drivers/ethernet/eth_adin2111.cADIN2111/ADIN1110 single-pair Ethernet devicesDevices using OA SPI (10BASE-T1S/T1L)
impact

Adjacent attacker can send crafted 10BASE-T1S/T1L frames to cause OOB writes, leading to DoS or potential remote code execution.

action required

Patch when possible

affected versions
zephyrproject zephyr
  • affected>= 3.7.0 and < 4.5.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free