An issue exists in the Virtual L2 receive handler `virtual recv()` within `subsys/net/l2/virtual/virtual.c` due to a fall-through path that incorrectly handles non-virtual interfaces. When `ethernet recv()` in `subsys/net/l2/ethernet/ethernet.c` passes an Ethernet interface to `virtual recv()`, the system treats the `ethernet api` as a `virtual interface api`. This causes the system to call `get config()` or `get capabilities()` instead of the intended `recv()` function.
This condition is triggered when a host sends an 802.1Q-tagged Ethernet frame on the same link and no attached virtual interface claims the frame, such as when a VLAN interface is administratively down. This leads to a mistyped indirect call where incorrect structures are passed to the driver, resulting in wild reads or writes to uninitialized memory. Additionally, the same issue is reachable via `any recv()` in `subsys/net/l2/dummy/any/any.c`, which causes an out-of-bounds read of the driver's API object. The impact is undefined behavior in the network RX path, leading to memory corruption and denial-of-service.