# CVE-2025-44559: Denial of service in n/a

> Attackers within Bluetooth range can cause a Denial of Service in Realtek RTL8762E BLE SDK by sending crafted control packets.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** No
- **Published:** 27 Jun 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-p345-93jf-pqg3

## What is CVE-2025-44559?

CVE-2025-44559 is a medium-severity denial of service vulnerability in n/a, published on 27 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in the Bluetooth Low Energy (BLE) stack of Realtek RTL8762E BLE SDK v1.4.0 allows attackers within Bluetooth range to cause a Denial of Service (DoS) via sending a specific sequence of crafted control packets.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2025-44559 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44559 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-44559 is a medium-severity denial of service vulnerability in n/a, published on 27 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44559 exists.

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-44559/ (Markdown: https://insights.sbomify.com/CVE-2025-44559/index.md)
```

## Sources

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

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