mac80211: Fix Locking in ieee80211_start_ap Error Path

Kernel Updated 02 Oct 2025

Summary

30/12/2021
N/A
No i
Unrated
Not published

GSD-2021-1002836: mac80211: fix locking in ieee80211_start_ap error path. Affects Kernel versions >= 295b02c4be74bebf988593b8322369513fcecf68, < c1d1ec4db5f7264cfc21993e59e8f2dcecf4b44f. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The mac80211 package is a subsystem in the Linux Kernel that provides the implementation of the IEEE 802.11 wireless networking stack. It is responsible for managing wireless network interfaces and handling various operations related to wireless communication. The ieee80211_start_ap function in mac80211 is used to start an access point (AP) mode on a wireless interface. However, there is a vulnerability in the error path of this function that leads to improper locking, potentially resulting in a race condition or other concurrency issues.

Vulnerability Detail

The vulnerability in mac80211's ieee80211_start_ap error path arises due to incorrect locking. When an error occurs during the initialization of the AP mode, the function fails to release the necessary locks, leading to a potential deadlock or other synchronization issues. An attacker may be able to exploit this vulnerability to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with elevated privileges. The impact and attack plausibility of this vulnerability have not been proven yet.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

No workaround has been provided for this vulnerability.

Conclusion

The mac80211 package in the Linux Kernel is vulnerable to a locking issue in the ieee80211_start_ap error path. This vulnerability can potentially lead to a denial-of-service (DoS) condition or arbitrary code execution. It is recommended to update the Linux Kernel to version v5.15.12 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

mac80211 is a subsystem in the Linux Kernel that provides the implementation of the IEEE 802.11 wireless networking stack.

ieee80211_start_ap is a function in mac80211 that is used to start an access point (AP) mode on a wireless interface.

The impact of this vulnerability is not yet proven, but it could potentially lead to a denial-of-service (DoS) condition or arbitrary code execution with elevated privileges.

To fix this vulnerability, update your Linux Kernel to version v5.15.12 or later.

No workaround has been provided for this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback