In the Linux kernel, the following vulnerability has been resolved:wifi: plfxlc: Remove erroneous assert in plfxlc_mac_releaseplfxlc_mac_release() asserts that mac->lock is held. This assertion isincorrect, because even if it was possible, it would not be the validbehaviour. The function is used when probe fails or after the device isdisconnected. In both cases mac->lock can not be held as the driver isnot working with the device at the moment. All functions that use mac->lockunlock it just after it was held. There is also no need to hold mac->lockfor plfxlc_mac_release() itself, as mac data is not affected, except formac->flags, which is modified atomically.This bug leads to the following warning:================================================================WARNING: CPU: 0 PID: 127 at drivers/net/wireless/purelifi/plfxlc/mac.c:106 plfxlc_mac_release+0x7d/0xa0Modules linked in:CPU: 0 PID: 127 Comm: kworker/0:2 Not tainted 6.1.124-syzkaller #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024Workqueue: usb_hub_wq hub_eventRIP: 0010:plfxlc_mac_release+0x7d/0xa0 drivers/net/wireless/purelifi/plfxlc/mac.c:106Call Trace:
No PoCs from references.
- https://github.com/runwhen-contrib/helm-charts
- https://github.com/w4zu/Debian_security