CVE-2026-42808: Buffer Overflow
An issue was discovered in Bosch Sensortec COINESSDK versions 2.0 through 2.11. The host streaming API function {{coinesreadstreamsensordata()}} fails to validate the boundaries of the caller-provided destination buffer. Internally, the stream processing mechanism in {{commintfprocessstreamresponse()}} discards the requested {{numberofsamples}} argument and copies the entirety of the streaming ring buffer's accumulated data into {{coinesstreamrspbuf}}. Subsequently, {{coinesreadstreamsensordata()}} unconditionally executes a {{memcpy}} of the ring buffer size into the caller-provided buffer without verifying if the destination memory allocation is large enough. A malicious or compromised hardware board connected via USB or BLE can exploit this by streaming a high volume of sensor samples, causing a heap or stack-based buffer overflow on the host desktop environment. This can result in a Denial of Service (DoS) or potential arbitrary code execution on the host machine.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Bosch Sensortec COINES_SDKto a version that resolves this vulnerability.Fixed in 2.11
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Host desktop environments using Bosch Sensortec COINES_SDK versions 2.0 through 2.11 and reading streamed sensor data from a connected hardware board are exposed. The affected connection paths identified are USB and BLE.
What does an attacker need to exploit it?
An attacker needs control of, or the ability to compromise, a hardware board connected to the host through USB or BLE. The board can then stream a high volume of sensor samples to overflow the caller-provided destination buffer.
Are applications affected only when they request many samples?
No. The internal stream processing discards the requested number_of_samples value and accumulates streaming ring-buffer data instead. The API then copies the full ring-buffer size into the caller-provided buffer without checking its allocation size.
What is the likely impact on an affected host?
Successful exploitation can cause a heap- or stack-based buffer overflow on the host desktop environment. The described consequences include denial of service and potential arbitrary code execution.