# CVE-2026-98460: Bluetooth: hci_sock: reject out-of-range OCF values

> An unprivileged local attacker can bypass Bluetooth HCI security filters by submitting out-of-range OCF values that alias allowlisted commands.

- **Severity:** Not scored
- **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:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-109296, BELL-CVE-2026-98460, DEBIAN-CVE-2026-98460, GHSA-66xw-2cgj-6x3v, UBUNTU-CVE-2026-98460

## What is CVE-2026-98460?

CVE-2026-98460 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: hci_sock: reject out-of-range OCF values

The raw HCI socket security filter has 128 OCF bits per supported OGF,
but masks the 10-bit OCF with 127 before looking up the command. An
unprivileged socket can therefore submit a reserved OCF that aliases an
allowlisted command modulo 128.

A conforming controller should reject reserved opcodes. Nevertheless,
the security decision must apply to the opcode that will actually be
sent, especially since controller-specific behavior is outside the host
stack's control.

Reject OCF values that cannot be represented by the security filter
instead of aliasing them onto an unrelated command.

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


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

Apply the vendor's patch.

## Is CVE-2026-98460 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98460 is a vulnerability in Linux, published on 18 Oct 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-98460 in the wild and no public exploit code.

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

## Sources

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

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