Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-93667Published 2026-11-16

CVE-2026-93667 — zephyrproject zephyr

medium

As of 2026-11-17, CVE-2026-93667 is a MEDIUM-severity vulnerability in zephyrproject zephyr, CVSS v3.1 5.9, EPSS 0.1% (7.7th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-93667 as of 2026-11-17; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
5.9/10Medium
EPSS
0.1%Higher than 7.7% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
3.3/10Threadlinqs triage score
Published
Updated 2026-11-17
CVSS v3.1 5.9 (MEDIUM) · EPSS 0.1% (higher than 7.7% of all scored CVEs) · Priority 3.3/10 · Published 2026-11-16

Last updated:

What is CVE-2026-93667?

The Virtual L2 receive handler virtual_recv() in subsys/net/l2/virtual/virtual.c ends with a fall-through path meant for a virtual interface that has nothing attached below it: it takes net_if_get_device(iface)->api, treats it as a struct virtual_interface_api, and calls api->recv(iface, pkt). That handler is however also invoked with a non-virtual interface: ethernet_recv() in subsys/net/l2/ethernet/ethernet.c deliberately passes the Ethernet interface so that a tagged frame can be dispatched over the VLAN interfaces attached to it. For an Ethernet interface dev->api is a struct ethernet_api, whose layout only shares the leading struct net_if_api, so the slot read as recv is actually get_config() (default) or get_capabilities() (when CONFIG_NET_STATISTICS_ETHERNET is enabled). The fall-through is reached whenever no attached virtual interface claims the frame - most simply when the VLAN interface owning the frame's tag exists but is administratively down, since net_eth_get_vlan_iface() resolves the tag without checking link state while virtual_recv() skips interfaces that are not up. Any host able to place an 802.1Q-tagged Ethernet frame on the same link can then trigger the mistyped indirect call; no authentication, IP reachability or user interaction is required, because the frame is consumed at L2 before any address check. The resulting call passes a struct net_if where the driver expects a struct device and a struct net_pkt where it expects a struct net_if , with the callee's remaining parameters left as whatever the call site happens to leave in the argument registers. Driver implementations dereference these values: get_capabilities() typically reads dev->config/dev->data (a wild read through a non-pointer field of struct net_if), and get_config() implementations write through the uninitialized struct ethernet_config * argument. The practical impact is undefined behaviour in the network RX path - crashes and uncontrolled memory corruption - plus mis-handling of the packet when a capability bitmask is returned as a net_verdict. The attacker controls neither the corrupted address nor the value written, so this is a denial-of-service and memory-corruption issue rather than a controllable write primitive. The same defective fall-through is reachable through any_recv() in subsys/net/l2/dummy/any/any.c, which passes a dummy interface whose struct dummy_api is shorter than the offset read, producing an out-of-bounds read of the driver's API object followed by an indirect call. The fix drops any packet whose interface is not a Virtual L2 interface, closing both entry points.

The record classifies CVE-2026-93667 under weakness classes CWE-686, CWE-688, CWE-843. Its CVSS v3 base vector states that the flaw is reachable from an adjacent network, needs no prior authentication, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 3 days ago.

Severity and exploitation probability

CVSS v3.1 base score
5.9 — MEDIUM
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 7.7% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
3.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-11-16

Is CVE-2026-93667 being exploited?

It currently carries a trending score of 32 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-93667

Patch reference: https://github.com/zephyrproject-rtos/zephyr/commit/226e821d8587aaae955b9682234b0b44722c8a4e. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-93667

No threat campaign in the Threadlinqs corpus currently references CVE-2026-93667, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references