CVE-2018-9419 is a high severity out-of-bounds read caused by a missing bounds check in the Bluetooth Low Energy L2CAP code (l2cble_process_sig_cmd in l2c_ble.cc). NVD scores it 7.5. Google fixes it at security patch level 2018-07-01 or later. Install the device update that reaches that level.
What's affected
- Product: Android, in the Bluetooth Low Energy L2CAP code (l2cble_process_sig_cmd in l2c_ble.cc).
- Releases listed by the bulletin: 7.0, 7.1.1, 7.1.2, 8.0 and 8.1. The NVD product list shows only some Android releases, so treat the bulletin as the fuller list.
- Fixed in: security patch level 2018-07-01 or later, according to the Android Security Bulletin for July 2018.
- Impact in the record: remote information disclosure with no privileges and no user interaction.
- Severity: NVD scores it 7.5 High (vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). The bulletin lists it as High, type ID. The two ratings agree.
- Weakness classes: CWE-125 (Out-of-bounds Read), 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-07-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-07-01 or later. - For a fleet, export the patch level from your mobile device management console and filter for dates earlier than 2018-07-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-07-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 record gives a 7.5 score with only confidentiality affected (C:H/I:N/A:N). Nothing is modified and nothing crashes in the scoring, but memory contents can leak to a remote peer.
An out-of-bounds read returns bytes from beyond the intended buffer. Those bytes may belong to other parts of the Bluetooth process. Leaks of this kind are often used to help other attacks, which is one reason they are fixed even when no code execution is involved. 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
If it only leaks data, can I wait?
The record rates impact as confidentiality only, but the bulletin still ranks it High. Because the fix ships in the same monthly patch level as other flaws, waiting rarely saves effort.
Which patch level should I look for?
The Android Security Bulletin for July 2018 places this fix at 2018-07-01. Any date at or after 2018-07-01 includes it. Some makers ship it under a different update name, so check the date.
Sources
- Android Security Bulletin for July 2018: Affected releases, severity, type and the patch level that carries the fix.
Last reviewed: 19 October 2026.
