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.
CVE-2026-16473
This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(low)
- EPSS
- —
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 22, 2026
Advisory Details (3)
Auto-updated Jul 22, 2026sbc.git - Bluetooth low-complexity, subband codec (SBC) library
https://git.kernel.org/pub/scm/bluetooth/sbc.git2503650 – (CVE-2026-16473) CVE-2026-16473 sbc: sbc: heap out-of-bounds read via crafted SBC audio frame
https://bugzilla.redhat.com/show_bug.cgi?id=2503650Vendor Advisories for CVE-2026-16473(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 11:38 UTCEG score recompute
- 2026-07-22 10:52 UTCEG score recompute
- 2026-07-22 10:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-125
- CVE-2014-2898EG 9.8CRITICAL
- CVE-2014-2897EG 9.8CRITICAL
- CVE-2014-2896EG 9.8CRITICAL
- CVE-2015-9290EG 9.8CRITICAL
- CVE-2016-10749EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS 96%CRITICAL
- CVE-2014-3180EG 9.1CRITICAL
- CVE-2014-1508EG 9.1EPSS 90%CRITICAL
- CVE-2016-5198NVD 8.8EG 9.0 KEVEPSS 98%HIGH
- CVE-2016-4523NVD 7.5EG 9.0 KEVEPSS 98%HIGH
Frequently asked(4)
What is CVE-2026-16473?
When was CVE-2026-16473 disclosed?
What is the CVSS score of CVE-2026-16473?
How do I remediate CVE-2026-16473?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16473
Is Your Infrastructure Affected by CVE-2026-16473?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.