wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 04f75f5bae33349283d6886901d9acd2f110c024, Kernel 058c9026ad79dc98572442fd4c7e9a36aba6f596, Kernel 07eb0bd7b0a8abed9d45e0f567c9af1dc83e5268 and 6 more.
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop() Since '__dev_queue_xmit()' should be called with interrupts enabled, the following backtrace: ieee80211_do_stop() ... spin_lock_irqsave(&local->queue_stop_reason_lock, flags) ... ieee80211_free_txskb() ieee80211_report_used_skb() ieee80211_report_ack_skb() cfg80211_mgmt_tx_status_ext() nl80211_frame_tx_status() genlmsg_multicast_netns() genlmsg_multicast_netns_filtered() nlmsg_multicast_filtered() netlink_broadcast_filtered() do_one_broadcast() netlink_broadcast_deliver() __netlink_sendskb() netlink_deliver_tap() __netlink_deliver_tap_skb() dev_queue_xmit() __dev_queue_xmit() ; with IRQS disabled ... spin_unlock_irqrestore(&local->queue_stop_reason_lock, flags) issues the warning (as reported by syzbot reproducer): WARNING: CPU: 2 PID: 5128 at kernel/softirq.c:362 __local_bh_enable_ip+0xc3/0x120 Fix this by implementing a two-phase skb reclamation in 'ieee80211_do_stop()', where actual work is performed outside of a section with interrupts disabled.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.32, >=5061b0c2b9066de426fbc63f1278d2210e789412 <04f75f5bae33349283d6886901d9acd2f110c024, >=5061b0c2b9066de426fbc63f1278d2210e789412 <058c9026ad79dc98572442fd4c7e9a36aba6f596, >=5061b0c2b9066de426fbc63f1278d2210e789412 <07eb0bd7b0a8abed9d45e0f567c9af1dc83e5268, >=5061b0c2b9066de426fbc63f1278d2210e789412 <9d301de12da6e1bb069a9835c38359b8e8135121, >=5061b0c2b9066de426fbc63f1278d2210e789412 <acb53a716e492a02479345157c43f21edc8bc64b, >=5061b0c2b9066de426fbc63f1278d2210e789412 <ad4b7068b101fbbb4a9ca4b99b25eb051a9482ec, >=5061b0c2b9066de426fbc63f1278d2210e789412 <db5ca4b42ccfa42d2af7b335ff12578e57775c02, >=5061b0c2b9066de426fbc63f1278d2210e789412 <eab272972cffff9cd973b8e4055a8e81c64f7e6a, >=5061b0c2b9066de426fbc63f1278d2210e789412 <f232916fab67ca1c3425926df4a866e59ff26908 | 04f75f5bae33349283d6886901d9acd2f110c024, 058c9026ad79dc98572442fd4c7e9a36aba6f596, 07eb0bd7b0a8abed9d45e0f567c9af1dc83e5268, 9d301de12da6e1bb069a9835c38359b8e8135121, acb53a716e492a02479345157c43f21edc8bc64b, ad4b7068b101fbbb4a9ca4b99b25eb051a9482ec, db5ca4b42ccfa42d2af7b335ff12578e57775c02, eab272972cffff9cd973b8e4055a8e81c64f7e6a, f232916fab67ca1c3425926df4a866e59ff26908 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket