# CVE-2026-105460: Bluez: bluez: stack-based out-of-bounds read in btmon via unvalidated num_keys in return_link_keys_evt()

> An attacker can cause a denial of service in the btmon tool by providing a crafted btsnoop capture file that triggers an out-of-bounds read.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2026-105460, DEBIAN-CVE-2026-105460, GHSA-hqj4-7q22-2hmj, UBUNTU-CVE-2026-105460

## What is CVE-2026-105460?

CVE-2026-105460 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 13 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in BlueZ. An out-of-bounds read vulnerability exists in the btmon Bluetooth monitor tool when processing crafted HCI Return Link Keys events. A maliciously crafted btsnoop capture file can specify a large number of link keys that exceeds the actual packet data, causing btmon to read beyond the allocated buffer and crash.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-105460 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105460 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 13 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-105460 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-105460/ (Markdown: https://insights.sbomify.com/CVE-2026-105460/index.md)
```

## Sources

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

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