In the Linux kernel, the following vulnerability has been resolved:
wifi: cfg80211: Set correct chandef when starting CAC
When starting CAC in a mode other than AP mode, it return a "WARNING: CPU: 0 PID: 63 at cfg80211chandefdfs_usable+0x20/0xaf [cfg80211]" caused by the chandef.chan being null at the end of CAC.
Solution: Ensure the channel definition is set for the different modes when starting CAC to avoid getting a NULL 'chan' at the end of CAC.
Call Trace: ? showregs.part.0+0x14/0x16 ? _warn+0x67/0xc0 ? cfg80211chandefdfsusable+0x20/0xaf [cfg80211] ? reportbug+0xa7/0x130 ? excoverflow+0x30/0x30 ? handlebug+0x27/0x50 ? excinvalidop+0x18/0x60 ? handleexception+0xf6/0xf6 ? excoverflow+0x30/0x30 ? cfg80211chandefdfsusable+0x20/0xaf [cfg80211] ? excoverflow+0x30/0x30 ? cfg80211chandefdfsusable+0x20/0xaf [cfg80211] ? regulatorypropagatedfsstate.cold+0x1b/0x4c [cfg80211] ? cfg80211propagatecacdonewk+0x1a/0x30 [cfg80211] ? processonework+0x165/0x280 ? workerthread+0x120/0x3f0 ? kthread+0xc2/0xf0 ? processonework+0x280/0x280 ? kthreadcompleteandexit+0x20/0x20 ? retfromfork+0x19/0x24
[shorten subject, remove OCB, reorder cases to match previous list]