CVE-2018-9475 is a high severity out-of-bounds stack write caused by a missing bounds check in the Bluetooth headset interface (HeadsetInterface::ClccResponse in btif_hf.cc). NVD scores it 8.8. Google fixes it at security patch level 2018-09-01 or later. Install the device update that reaches that level.
What's affected
- Product: Android, in the Bluetooth headset interface (HeadsetInterface::ClccResponse in btif_hf.cc).
- Releases listed by the bulletin: 7.0, 7.1.1, 7.1.2, 8.0, 8.1 and 9. The NVD product list shows only some Android releases, so treat the bulletin as the fuller list.
- Fixed in: security patch level 2018-09-01 or later, according to the Android Security Bulletin for September 2018.
- Impact in the record: remote escalation of privilege via Bluetooth if the recipient has enabled SIP calls, with no user interaction.
- Severity: NVD scores it 8.8 High (vector AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The bulletin lists it as Critical, type EoP. Both ratings are given because they differ.
- Weakness classes: CWE-787 (Out-of-bounds Write).
How to check if you're exposed
- On the device, open Settings and find the Android security patch level, usually under About phone. The exact path varies by manufacturer. A date earlier than 2018-09-01 means the fix is not present.
- With a USB debugging connection, run
adb shell getprop ro.build.version.security_patch. It prints the patch level as a date. You need 2018-09-01 or later. - For a fleet, export the patch level from your mobile device management console and filter for dates earlier than 2018-09-01.
- Match each device against the release list above. Devices on releases outside it are not named for this CVE, but check them against the other entries in the same bulletin.
What to do now
- Identify every Android device in scope and record its current security patch level.
- Roll out the manufacturer or carrier update that reaches 2018-09-01 or later. Google publishes the fixes, but each device maker decides when its devices receive them.
- For devices that no longer receive updates, plan replacement or limit what they can reach, such as corporate mail and internal apps.
- Until patched, turn Bluetooth off when you do not need it and avoid pairing with unknown devices. This lowers exposure but does not replace the update.
- Write the update policy down, with a maximum patch age, and report exceptions.
Why it matters
The vector is adjacent network (AV:A), meaning the attacker must be within Bluetooth range. The description adds a condition: the recipient has enabled SIP calls. NVD scores 8.8 High, while the bulletin rates it Critical.
Call list responses carry data from a remote peer, and the handler copied it into a stack buffer without enough checking. Stack writes past the end of a buffer are the oldest class of memory corruption, and they are still fixed in current code every month. The record's KEV flag is false, so CISA does not list it as exploited. The bulletin says Google had no reports of active customer exploitation or abuse of the newly reported issues in it. That is the absence of a report in the sources read, not proof that no one has tried.
Quick check
Who is exposed by the SIP condition?
The description says exposure applies if SIP calls are enabled on the recipient device. Devices that do not use SIP calling are in a better position, but the patch is still the fix.
Which patch level should I look for?
The Android Security Bulletin for September 2018 places this fix at 2018-09-01. Any date at or after 2018-09-01 includes it. Some makers ship it under a different update name, so check the date.
Sources
- Android Security Bulletin for September 2018: Affected releases, severity, type and the patch level that carries the fix.
Last reviewed: 19 October 2026.