CVE-2023-27349 is a high severity (CVSS 8.0 in the record, 7.1 at ZDI) array index validation flaw in the AVRCP audio profile of BlueZ, the Linux Bluetooth stack. A nearby device could trigger code execution. BlueZ fixed it in a commit; update to a build that includes it.
What's affected
The record lists BlueZ 5.66 in its product data. The Zero Day Initiative advisory ZDI-23-386 names BlueZ without a version and says BlueZ has issued an update, pointing to a commit in the BlueZ repository (commit f54299a8). I could not load the commit page, which sat behind a bot check. The record also links two Debian LTS announcements, which indicate that distributions shipped fixes, but their pages needed JavaScript and I could not read the package versions.
Severity differs. The record shows 8.0 with an adjacent network vector, low complexity, no privileges and user interaction required. ZDI shows 7.1, with high attack complexity. Both are high.
The cause per ZDI is a lack of proper validation of user supplied data in the AVRCP protocol handling, resulting in a write past the end of an allocated buffer. The weakness is CWE-129, improper validation of an array index. ZDI says the attacker gains code execution in the context of root, and that the target must connect to a malicious device. ZDI reported it to the vendor on 22 March 2023 and published on 12 April 2023.
How to check if you're exposed
On a Linux system:
bluetoothd --version
dpkg -l | grep -i bluez
rpm -qa | grep -i bluez
BlueZ 5.66 is named in the record. Distributions backport fixes, so a version number alone may not tell you if the fix is present. Check your distribution's security tracker or changelog for CVE-2023-27349. The Debian LTS announcements linked from the record cover Debian users. For embedded devices, such as car head units, industrial gear or set top boxes, ask the device maker.
To see which of your own applications pull in affected components, run the free in-browser dependency scan at gold.safeguard.sh/scan.
What to do now
- List systems that run BlueZ, including embedded and IoT devices with Bluetooth audio.
- Check your distribution changelog or tracker for a fix for CVE-2023-27349 and install the update.
- If you build BlueZ yourself, make sure your source includes the upstream fix commit.
- Turn off Bluetooth on systems that do not need it.
- Disable automatic pairing and discoverable mode where you can.
Why it matters
Bluetooth stacks parse data from devices that the user may not control. If the code uses an index from a message without checking it, an attacker can make it write beyond the buffer. ZDI says the result could be code execution as root, which is a strong outcome for a feature people enable casually.
The attacker must be nearby and the user has to connect to a malicious device, so it is not an internet wide problem. For laptops, kiosks and embedded devices in public places the distance is a smaller shield. The record does not flag CISA KEV and ZDI describes a coordinated release.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Do I need to be near the attacker?
Yes. ZDI describes a network adjacent attacker, and the target must connect to a malicious device.
Is 5.66 the only affected version?
The record names 5.66 only. Other versions may be affected, so check your distribution tracker.
Sources
- ZDI-23-386
- BlueZ fix commit (referenced in the record; page behind a bot check)
- Debian LTS announcement, May 2024 (referenced in the record)
- Gold entry
Last reviewed: 19 October 2026.