# CVE-2025-27558: Other in n/a

> Attackers can inject arbitrary frames into Wi-Fi mesh networks, bypassing security protections and modifying data on affected devices.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2025
- **Updated:** 3 Nov 2025
- **Also known as:** BELL-CVE-2025-27558, DEBIAN-CVE-2025-27558, GHSA-hchj-55px-fgw7, ROOT-OS-UBUNTU-2204-CVE-2025-27558, UBUNTU-CVE-2025-27558

## What is CVE-2025-27558?

CVE-2025-27558 is a critical vulnerability in n/a, published on 21 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IEEE P802.11-REVme D1.1 through D7.0 allows FragAttacks against mesh networks. In mesh networks using Wi-Fi Protected Access (WPA, WPA2, or WPA3) or Wired Equivalent Privacy (WEP), an adversary can exploit this vulnerability to inject arbitrary frames towards devices that support receiving non-SSP A-MSDU frames. NOTE: this issue exists because of an incorrect fix for CVE-2020-24588. P802.11-REVme, as of early 2025, is a planned release of the 802.11 standard.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2025-27558?


## How do I fix CVE-2025-27558?

Apply the vendor's patch.

## Is CVE-2025-27558 being exploited?

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

Public exploit code:

- Patching CVE-2025-27558 vulnerability that had affected my linux image. (github_poc): https://github.com/Atlas-ghostshell/CVE-2025-27558_Patching

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27558 and fix it if it is affected.

What it is: CVE-2025-27558 is a critical vulnerability in n/a, published on 21 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27558 in the wild and no public exploit code.

Affected product: n/a. 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-2025-27558/ (Markdown: https://insights.sbomify.com/CVE-2025-27558/index.md)
```

## Sources

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

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