wifi: mac80211: don't start a ROC while scanning
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.112, 6.18.54, 7.2.8
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don't start a ROC while scanning The ROC work can be pending when a scan starts (which requires ROC list to be empty, but that's possible), and then a new ROC can be added to the list and the work will pick it up. Avoid starting that ROC if a scan made it between things, as otherwise we'll hit a warning later: WARNING: net/mac80211/offchannel.c:404 at ieee80211_start_next_roc+0x256/0x2d0 Workqueue: events_unbound cfg80211_wiphy_work Call Trace: __ieee80211_scan_completed+0x4fd/0xe40 net/mac80211/scan.c:537 ieee80211_scan_work+0x472/0x1ff0 net/mac80211/scan.c:1193 cfg80211_wiphy_work+0x410/0x570 net/wireless/core.c:513
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From aaa016ccd5df89d73483d0d51ee1f692978ccc35 · fixed in 5dc8ec2f8d1d62914661577c23ec151f5c9734a4; From aaa016ccd5df89d73483d0d51ee1f692978ccc35 · fixed in 81baab8b645ec532bad2b7a8464191c720ef8fd9; From aaa016ccd5df89d73483d0d51ee1f692978ccc35 · fixed in 58b806f699052c572dec6cab2c376f884f27e98f; From aaa016ccd5df89d73483d0d51ee1f692978ccc35 · fixed in 733f0fde95392ed5f61a4e36aee661ea8d0e8581
- Linux Linux
4.5
- KernelLinux
From 4.5.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.54; From 6.19.0 · fixed in 7.2.8