# CVE-2021-0075: Memory corruption in Intel(R) PROSet/Wireless WiFi in multiple operating systems and some Killer(TM) WiFi in Windows 10

> A privileged local attacker can cause a denial of service via an out-of-bounds write in Intel and Killer WiFi firmware.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** No
- **Published:** 17 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4qgw-9vrf-6w24

## What is CVE-2021-0075?

CVE-2021-0075 is a medium-severity memory corruption vulnerability in Intel(R) PROSet/Wireless WiFi in multiple operating systems and some Killer(TM) WiFi in Windows 10, published on 17 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out-of-bounds write in firmware for some Intel(R) PROSet/Wireless WiFi in multiple operating systems and some Killer(TM) WiFi in Windows 10 may allow a privileged user to potentially enable denial of service via local access.

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

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

It affects 16 products.


Products: Intel 7265 Firmware, Intel 9260 Firmware, Intel Ac1550 Firmware, Intel Ac 3165 Firmware, Intel Ac 3168 Firmware, Intel Ac 8260 Firmware, Intel Ac 8265 Firmware, Intel Ac 9260 Firmware, Intel Ac 9461 Firmware, Intel Ac 9462 Firmware, Intel Ac 9560 Firmware, Intel Ax1650 Firmware, Intel Ax1675 Firmware, Intel Ax200 Firmware, Intel Ax201 Firmware, Intel Ax210 Firmware.

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

No fix has been published for CVE-2021-0075 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-0075 being exploited?

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

## Other vulnerabilities in Intel(R) PROSet/Wireless WiFi in multiple operating systems and some Killer(TM) WiFi in Windows 10

- [CVE-2021-0071](https://insights.sbomify.com/CVE-2021-0071/): Privilege escalation in Intel(R) PROSet/Wireless WiFi in UEFI (high 8.8)
- [CVE-2021-0078](https://insights.sbomify.com/CVE-2021-0078/): Denial of service in Intel(R) PROSet/Wireless WiFi and Killer(TM) WiFi in Windows 10 (high 8.1)
- [CVE-2021-0064](https://insights.sbomify.com/CVE-2021-0064/): Privilege escalation in Intel(R) PROSet/Wireless WiFi software installer for Windows 10 (high 7.8)
- [CVE-2021-0065](https://insights.sbomify.com/CVE-2021-0065/): Privilege escalation in Intel(R) PROSet/Wireless WiFi software installer for Windows 10 (high 7.8)
- [CVE-2021-0082](https://insights.sbomify.com/CVE-2021-0082/): Privilege escalation in Intel(R) PROSet/Wireless WiFi in Windows 10 (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-0075 is a medium-severity memory corruption vulnerability in Intel(R) PROSet/Wireless WiFi in multiple operating systems and some Killer(TM) WiFi in Windows 10, published on 17 Nov 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-0075 in the wild and no public exploit code.

Affected product: Intel(R) PROSet/Wireless WiFi in multiple operating systems and some Killer(TM) WiFi in Windows 10. 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-0075/ (Markdown: https://insights.sbomify.com/CVE-2021-0075/index.md)
```

## Sources

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

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