Cloudanix VulnDB

CVE-2016-9803

Medium · 5.3

CVSS

5.3

EPSS

2.7%

Published

Dec 3, 2016

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A Bluetooth processing error can make affected software crash when it receives unexpected messages, potentially interrupting operations until fixed packages are installed.

Exploit Available
Exploitation
Remote Unauthenticated
Attacker needs
None
Complexity
Low
Impact
Denial Of Service
Component
Library
Class
Memory Corruption
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Out-of-bounds read in the le_meta_ev_dump function caused by an overflowed subevent index into the ev_le_meta_str array, resulting in memory corruption and potential denial of service.

Why it matters to the business

Service availability can be disrupted on systems processing Bluetooth HCI events, with minor exploit probability that has increased modestly over the past month; the issue affects downstream packages built from vulnerable components and carries a multi-year-old remediation deadline.

How an attack unfolds

An attacker sends a crafted Bluetooth HCI event packet containing an out-of-range subevent value; the parser in tools/parser/hci.c uses this value without bounds checking to index the meta event array, triggering the out-of-bounds read and possible crash.

How to fix it

Upgrade falcosidekick (Chainguard) to 2.28.0-r7 or later and falcosidekick (Wolfi) to 2.28.0-r7 or later; rebuild any dependent images with updated BlueZ components that correct the HCI parser bounds check.

How to confirm the fix worked

Confirm package versions match or exceed the listed fixed releases, then run regression tests that exercise HCI event parsing with boundary-value subevent inputs to verify absence of crashes.

Typical attack path

  1. Craft malicious LE meta event packet with oversized subevent field
  2. Deliver packet over Bluetooth or emulated HCI channel to target
  3. Trigger parsing path that calls le_meta_ev_dump
  4. Induce out-of-bounds read leading to process crash or instability

How to detect it

Review system and application logs for unexpected crashes or errors originating from HCI parsing routines; look for unusual Bluetooth event traffic patterns around the time of any availability incidents.

What your security team should do

  • Apply the specified package upgrades immediately on all affected builds
  • Scan container images and CI pipelines for remaining vulnerable BlueZ parser code
  • Monitor EPSS trend and exploit availability for any increase in observed attempts

The record

In BlueZ 5.42, an out-of-bounds read was observed in "le_meta_ev_dump" function in "tools/parser/hci.c" source file. This issue exists because 'subevent' (which is used to read correct element from 'ev_le_meta_str' array) is overflowed.

Affected packages

Ecosystem Package Introduced Fixed
Debian:10 bluez 0 No fix
Debian:11 bluez 0 No fix
Debian:12 bluez 0 No fix
Debian:13 bluez 0 No fix
SUSE:Linux Enterprise Server 12 SP2-BCL bluez 0 5.13-5.31.1
SUSE:Linux Enterprise Server 12 SP3-BCL bluez 0 5.13-5.31.1
SUSE:Linux Enterprise Server 12 SP4-LTSS bluez 0 5.13-5.31.1
SUSE:Linux Enterprise Server 12 SP5 bluez 0 5.13-5.31.1
SUSE:Linux Enterprise Server for SAP Applications 12 SP4 bluez 0 5.13-5.31.1
SUSE:Linux Enterprise Server for SAP Applications 12 SP5 bluez 0 5.13-5.31.1
SUSE:Linux Enterprise Software Development Kit 12 SP5 bluez 0 5.13-5.31.1
SUSE:Linux Enterprise Workstation Extension 12 SP5 bluez 0 5.13-5.31.1
SUSE:OpenStack Cloud 9 bluez 0 5.13-5.31.1
SUSE:OpenStack Cloud Crowbar 9 bluez 0 5.13-5.31.1
Ubuntu:20.04:LTS bluez 0 No fix
Ubuntu:22.04:LTS bluez 0 No fix
Ubuntu:24.04:LTS bluez 0 No fix
Ubuntu:24.10 bluez 0 No fix
Ubuntu:25.04 bluez 0 No fix
Ubuntu:25.10 bluez 0 No fix
Ubuntu:Pro:16.04:LTS bluez 0 No fix
Ubuntu:Pro:18.04:LTS bluez 0 No fix
Ubuntu:Pro:20.04:LTS bluez 0 No fix

Related vulnerabilities