# CVE-2021-47194: cfg80211: call cfg80211_stop_ap when switch from P2P_GO type

> A missing cleanup call in the Linux kernel Wi-Fi subsystem can corrupt linked lists, potentially leading to system crashes or code execution.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Apr 2024
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2021-47194, GHSA-p3j3-7q7c-3g53, UBUNTU-CVE-2021-47194

## What is CVE-2021-47194?

CVE-2021-47194 is a high-severity memory corruption vulnerability in Linux kernel, published on 10 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

cfg80211: call cfg80211_stop_ap when switch from P2P_GO type

If the userspace tools switch from NL80211_IFTYPE_P2P_GO to
NL80211_IFTYPE_ADHOC via send_msg(NL80211_CMD_SET_INTERFACE), it
does not call the cleanup cfg80211_stop_ap(), this leads to the
initialization of in-use data. For example, this path re-init the
sdata->assigned_chanctx_list while it is still an element of
assigned_vifs list, and makes that linked list corrupt.

Weakness: CWE-665 (Improper Initialization)

## Which versions are affected by CVE-2021-47194?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2021-47194?

Apply the vendor's patch.

## Is CVE-2021-47194 being exploited?

There is no known exploitation of CVE-2021-47194 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-47194 and fix it if it is affected.

What it is: CVE-2021-47194 is a high-severity memory corruption vulnerability in Linux kernel, published on 10 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-47194 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-47194/ (Markdown: https://insights.sbomify.com/CVE-2021-47194/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-47194
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-47194
- OSV: https://osv.dev/vulnerability/CVE-2021-47194

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-47194/
Summaries are generated and may contain mistakes; the official description above is the record.