# CVE-2026-16473: Sbc: sbc: heap out-of-bounds read via crafted sbc audio frame

> An off-by-one error in the SBC decoder allows adjacent attackers to read one byte of heap memory via crafted Bluetooth audio frames.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 22 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** AZL-93096, BELL-CVE-2026-16473, DEBIAN-CVE-2026-16473, ECHO-3bf2-b44c-e0e9, GHSA-2xmm-4jcc-wgxq, UBUNTU-CVE-2026-16473, openSUSE-SU-2026:12113-1

## What is CVE-2026-16473?

CVE-2026-16473 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 22 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in the sbc library (BlueZ SBC codec). An off-by-one error in the SBC frame decoder allows a crafted audio payload to trigger a one-byte heap out-of-bounds read. This could allow an adjacent attacker streaming Bluetooth audio to read a single byte of adjacent heap memory.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sbc` | openSUSE:Tumbleweed | All versions | 2.2-2.1 |

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

Apply the vendor's patch.

## Is CVE-2026-16473 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16473 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 22 Jul 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-16473 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-16473/ (Markdown: https://insights.sbomify.com/CVE-2026-16473/index.md)
```

## Sources

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

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