CVE-2024-47713: wifi: mac80211: use two-phase skb reclamation in ieee80211_do_stop()

Published Oct 21, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

wifi: mac80211: use two-phase skb reclamation in ieee80211dostop()

Since 'devqueuexmit()' should be called with interrupts enabled, the following backtrace:

ieee80211dostop() ... spinlockirqsave(&local->queuestopreasonlock, flags) ... ieee80211freetxskb() ieee80211reportusedskb() ieee80211reportackskb() cfg80211mgmttxstatusext() nl80211frametxstatus() genlmsgmulticastnetns() genlmsgmulticastnetnsfiltered() nlmsgmulticastfiltered() netlinkbroadcastfiltered() doonebroadcast() netlinkbroadcastdeliver() netlinksendskb() netlinkdelivertap() netlinkdelivertapskb() devqueuexmit() devqueuexmit() ; with IRQS disabled ... spinunlockirqrestore(&local->queuestopreasonlock, flags)

issues the warning (as reported by syzbot reproducer):

WARNING: CPU: 2 PID: 5128 at kernel/softirq.c:362 localbhenableip+0xc3/0x120

Fix this by implementing a two-phase skb reclamation in 'ieee80211dostop()', where actual work is performed outside of a section with interrupts disabled.

Other sources

In the Linux kernel, the following vulnerability has been resolved:

wifi: mac80211: use two-phase skb reclamation in ieee80211dostop()

Since 'devqueuexmit()' should be called with interrupts enabled, the following backtrace:

ieee80211dostop() ... spinlockirqsave(&local->queuestopreasonlock, flags) ... ieee80211freetxskb() ieee80211reportusedskb() ieee80211reportackskb() cfg80211mgmttxstatusext() nl80211frametxstatus() genlmsgmulticastnetns() genlmsgmulticastnetnsfiltered() nlmsgmulticastfiltered() netlinkbroadcastfiltered() doonebroadcast() netlinkbroadcastdeliver() netlinksendskb() netlinkdelivertap() netlinkdelivertapskb() devqueuexmit() devqueuexmit() ; with IRQS disabled ... spinunlockirqrestore(&local->queuestopreasonlock, flags)

issues the warning (as reported by syzbot reproducer):

WARNING: CPU: 2 PID: 5128 at kernel/softirq.c:362 localbhenableip+0xc3/0x120

Fix this by implementing a two-phase skb reclamation in 'ieee80211dostop()', where actual work is performed outside of a section with interrupts disabled.

NVD

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

8 affected componentsFixes available
Linux Linux kernel>=2.6.32<5.10.227
Linux Linux kernel>=5.11<5.15.168
Linux Linux kernel>=5.16<6.1.113
Linux Linux kernel>=6.2<6.6.54
Linux Linux kernel>=6.7<6.10.13
Linux Linux kernel>=6.11<6.11.2
debian/linux<=5.10.223-1
5.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1

Event History

Oct 21, 2024
CVE Published
via MITRE·11:53 AM
Data Sourced
via MITRE·11:53 AM
Description
Data Sourced
via NVD·12:15 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Red Hat·01:04 PM
DescriptionSeverityAffected Software
Feb 12, 2025
Data Sourced
via Launchpad·05:14 AM
Description
Apr 29, 2025
Data Sourced
via Ubuntu·06:25 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-47713?

The severity of CVE-2024-47713 is currently classified as high due to its potential impact on system stability and security.

2

How do I fix CVE-2024-47713?

To fix CVE-2024-47713, update to the latest stable version of the Linux kernel, specifically versions 6.1.123-1, 6.1.128-1, or higher.

3

Which versions of the Linux kernel are affected by CVE-2024-47713?

CVE-2024-47713 affects Linux kernel versions between 2.6.32 and 6.10.13, including specific ranges within those versions.

4

What components are impacted by CVE-2024-47713 in the Linux kernel?

CVE-2024-47713 specifically impacts the mac80211 component of the Linux kernel, which is related to Wi-Fi functionalities.

5

Is CVE-2024-47713 actively being exploited?

At this time, there is no public report indicating that CVE-2024-47713 is actively being exploited in the wild.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203