# CVE-2026-80186: Bluez: stack overflow in name2utf8 causes dos and potential code execution

> Remote attackers can crash the Bluetooth service or execute arbitrary code via crafted EIR packets during discovery in BlueZ.

- **Severity:** High 7.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 25 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-80186, DEBIAN-CVE-2026-80186, GHSA-f784-6479-v89p, ROOT-OS-DEBIAN-11-CVE-2026-80186, ROOT-OS-DEBIAN-12-CVE-2026-80186, ROOT-OS-DEBIAN-13-CVE-2026-80186, UBUNTU-CVE-2026-80186

## What is CVE-2026-80186?

CVE-2026-80186 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 25 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A stack-based buffer overflow vulnerability exists in BlueZ, the Linux Bluetooth protocol stack. A remote user within Bluetooth radio range can send a specially crafted Extended Inquiry Response (EIR) packet that causes a buffer overflow when the target device performs Bluetooth discovery. This vulnerability can lead to a Denial of Service (DoS) by crashing the bluetoothd service and may allow for arbitrary code execution.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2026-80186?


## How do I fix CVE-2026-80186?

Apply the vendor's patch.

## Is CVE-2026-80186 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80186 and fix it if it is affected.

What it is: CVE-2026-80186 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 25 Aug 2026. 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-2026-80186 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 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-2026-80186/ (Markdown: https://insights.sbomify.com/CVE-2026-80186/index.md)
```

## Sources

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

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