# CVE-2021-0326: Memory corruption in Android

> Remote attackers can execute arbitrary code on Android devices via a Wi-Fi Direct search due to an out-of-bounds write in the P2P component.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** A-172937525, ALPINE-CVE-2021-0326, ASB-A-172937525, DEBIAN-CVE-2021-0326, DLA-2572-1, GHSA-4wv8-p854-pjqv, MGASA-2021-0075, OESA-2021-1364, RHSA-2021:1686, RLSA-2021:1686, SUSE-SU-2021:0443-1, SUSE-SU-2021:0477-1, UBUNTU-CVE-2021-0326, openSUSE-SU-2021:0284-1

## What is CVE-2021-0326?

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

### Official description

In p2p_copy_client_info of p2p.c, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution if the target device is performing a Wi-Fi Direct search, with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-8.1 Android-9Android ID: A-172937525

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wpa_supplicant` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.9-5.el8 |
| `wpa_supplicant-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.9-5.el8 |
| `wpa_supplicant-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 1:2.9-5.el8 |
| `wpa_supplicant` | Rocky Linux:8 | All versions | 1:2.9-5.el8 |
| `wpa_supplicant` | SUSE:Enterprise Storage 6 | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise Module for Basesystem 15 SP2 | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 2.9-23.6.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise Server 15 SP1-BCL | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise Server 15-LTSS | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 2.9-23.6.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | SUSE:Manager Proxy 4.0 | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | SUSE:Manager Retail Branch Server 4.0 | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | SUSE:Manager Server 4.0 | All versions | 2.9-4.23.1 |
| `wpa_supplicant` | openSUSE:Leap 15.2 | All versions | 2.9-lp152.8.6.1 |

Products: Debian Debian Linux, Fedoraproject Fedora, Google Android.

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

Apply the vendor's patch.

## Is CVE-2021-0326 being exploited?

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

Public exploit code:

- Skeleton (but pronounced like Peloton): A Zero-Click RCE exploit for CVE-2021-0326 (github_poc): https://github.com/aemmitt-ns/skeleton
- https://github.com/nanopathi/wpa_supplicant_8_CVE-2021-0326. (github_poc): https://github.com/nanopathi/wpa_supplicant_8_CVE-2021-0326.
- https://github.com/Satheesh575555/external_wpa_supplicant_8_AOSP10_r33_CVE-2021-0326 (github_poc): https://github.com/Satheesh575555/external_wpa_supplicant_8_AOSP10_r33_CVE-2021-0326
- https://github.com/nanopathi/Packages_wpa_supplicant8_CVE-2021-0326 (github_poc): https://github.com/nanopathi/Packages_wpa_supplicant8_CVE-2021-0326
- https://github.com/ShaikUsaf/external_wpa_supplicant_8_AOSP10_r33CVE-2021-0326 (github_poc): https://github.com/ShaikUsaf/external_wpa_supplicant_8_AOSP10_r33CVE-2021-0326

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-0326 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 10 Feb 2021. 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-0326 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-0326/ (Markdown: https://insights.sbomify.com/CVE-2021-0326/index.md)
```

## Sources

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

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