Alexis Lothoré

**Name of the Vulnerable Software and Affected Versions** Linux kernel versions prior to the version containing the fix for the issue described **Description** A specific error path in probe functions in wilc drivers can lead to a kernel panic. This issue is due to a recent change decoupling wiphy allocation from wiphy registration, but the `wilc netdev cleanup` function has not been updated accordingly, allowing it to possibly call `wiphy unregister` on a wiphy that has never been registered. The issue can be reproduced by not wiring a wilc device correctly through SPI, making it unresponsive to early SPI commands. **Recommendations** To resolve the issue, move `wiphy unregister` and `wiphy free` out of `wilc netdev cleanup`, and adjust error paths in both drivers. As a temporary workaround, consider disabling the `wilc netdev cleanup` function until a patch is available. Restrict access to the vulnerable `wilc1000` module to minimize the risk of exploitation. Avoid using the `wilc1000` driver with SPI devices that are not properly wired until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Linux kernel versions prior to 6.7.0-rc1-wt+ **Description** The issue arises from incorrect RCU usage in the connect path of the wifi component, specifically in the `wilc parse join bss param()` function. When lockdep is enabled, calls to the connect function from the cfg802.11 layer lead to a warning about suspicious RCU usage. This warning is emitted because the code dereferences an RCU pointer without being in an RCU critical section. The fix involves moving the RCU dereference to a RCU read critical section to avoid this issue. **Recommendations** To resolve this issue, update the Linux kernel to a version that includes the fix for the RCU usage in the connect path. Specifically, versions 6.7.0-rc1-wt and later should include this fix. If updating is not immediately possible, consider applying the patch that moves the RCU dereference to a RCU read critical section manually. However, this should be done with caution and only by experienced developers or system administrators. At the moment, there is no information about other workarounds or mitigation measures for this specific issue.