The ocelot driver contained a race condition because the function that transmits injected frames did not hold the required injection group lock. This code path can corrupt kernel state or cause a crash when concurrent accesses occur, leading to a denial of service. The missing lock protection creates a scenario where attacker‑controlled driver interactions or crafted network traffic could trigger the race, potentially exposing the system to critical instability or exploitation if the attacker crafts input to corrupt memory.

All Linux kernel releases that contain the ocelot network driver before the patch that introduces lock protection around the registration injection path are affected. The issue is tied to the ocelot driver implementation used in kernel versions prior to the inclusion of the missing lock fix.

No EPSS score is available, and the vulnerability is not listed in CISA's KEV catalog, indicating that widespread exploitation has not been observed. However, because the flaw involves a race condition in kernel space, the potential impact is severe when an attacker can influence network traffic directed to the affected driver. The likely attack vector is a local or remote attacker who can generate traffic processed by the ocelot driver to trigger the race, causing a kernel crash or data corruption.