# CVE-2026-101887: BlueALSA bluealsad LC3plus Decoder Division-by-Zero DoS

> A Bluetooth-adjacent attacker can crash the BlueALSA daemon by sending a crafted RTP header with a zero frame count, causing a division-by-zero error.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** No
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-101887, GHSA-r27r-cp4v-gw48, UBUNTU-CVE-2026-101887

## What is CVE-2026-101887?

CVE-2026-101887 is a low-severity denial of service vulnerability in arkq bluez-alsa, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

BlueALSA (bluez-alsa/bluealsad) contains a division-by-zero vulnerability in the LC3plus sink decoder (a2dp-lc3plus.c, a2dp_lc3plus_dec_thread) that allows a Bluetooth-adjacent attacker to crash the daemon by sending a crafted RTP media header with an attacker-controlled frame count field set to zero. Attackers can establish an A2DP source connection with an LC3plus session negotiated against a victim running bluealsad as an A2DP sink and transmit a non-fragmented LC3plus media header with a zero frame count to trigger a SIGFPE in the decoding thread, causing a denial of service on builds compiled with LC3plus support enabled.

Weakness: CWE-369 (Divide By Zero)

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


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

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

## Is CVE-2026-101887 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101887 is a low-severity denial of service vulnerability in arkq bluez-alsa, published on 1 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-101887 in the wild and no public exploit code.

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

## Sources

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

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