CVE-2018-9388 is a critical severity flaw in Android: out of bounds writes in store_upgrade and store_cmd of ftm4_pdc.c. NVD scores it 9.8. Google fixed it in the June 2018 Pixel and Nexus Security Bulletin. Devices at security patch level 2018-06-05 or later are covered, so check the level and update.
What's affected
The weakness is out of bounds writes in store_upgrade and store_cmd of ftm4_pdc.c, in the ftm4 touchscreen driver. The bulletin entry is typed EoP and its affected versions column reads: not given as a version; the bulletin lists the component as ftm4_touch. The NVD record is dated 2024-12-05 and carries the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
The two sources disagree on severity. Google's bulletin rates it Moderate, while NVD scores it 9.8 (Critical). Both are published figures and both are reported here. The NVD record gives no Android version for this issue, so the component named in the bulletin is the better guide.
The fix is a platform patch, not something you install per app. Per the June 2018 bulletin, security patch levels of 2018-06-05 or later address all issues in that bulletin. Google devices (Pixel and Nexus) receive the fix at that level, and other manufacturers ship it on their own schedule.
Weakness class: CWE-191, CWE-787.
How to check if you're exposed
Look at the security patch level, not the Android version number. The patch level is the date string that shows which monthly bulletins a device has absorbed.
On the device, open Settings, then About phone, then Android version, and read the Android security patch level. Exact menus vary by manufacturer.
For managed devices with USB debugging enabled, this reads the same value:
adb shell getprop ro.build.version.security_patch
adb shell getprop ro.build.version.release
A patch level earlier than 2018-06-05 means this bulletin has not been fully applied. A device that no longer receives updates cannot be fixed this way and should be retired from sensitive use.
What to do now
- Find every Android device that touches company data and record its patch level, using your mobile device management tool or the commands above.
- Update devices below 2018-06-05 through the manufacturer or carrier channel.
- For devices that cannot reach that level, restrict access to email, source code and admin tools, or replace them.
- Set a compliance rule that blocks devices more than a set number of months behind on patch level.
- Read the original entry in the June 2018 bulletin for anything specific to your hardware.
Why it matters
The record says store_upgrade and store_cmd in the ftm4 touchscreen driver have out of bounds writes, from missing bounds checks or integer underflows. These could lead to escalation of privilege.
The weaknesses are CWE-191, integer underflow, and CWE-787, out of bounds write. The NVD vector says network, no privileges and no interaction, which is why it scores 9.8, yet the description speaks only of escalation of privilege and the bulletin calls it Moderate. The two ratings are far apart, so check the original bulletin before deciding how fast to move.
This CVE is not on the CISA Known Exploited Vulnerabilities list, and I found no statement of exploitation in the bulletin. That is not a reason to wait. Old Android issues linger because many devices never receive the monthly updates, and the record was only published to NVD in 2024, years after the bulletin.
Safeguard's free in-browser dependency scan at gold.safeguard.sh/scan covers the libraries your own apps ship, not the device operating system. Use it for the app side, and your device management tool for the patch level side.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Which patch level fixes CVE-2018-9388?
Google's June 2018 bulletin says security patch levels of 2018-06-05 or later address its issues. Confirm the exact entry in the bulletin for your device and manufacturer.
Is CVE-2018-9388 exploited in the wild?
It is not listed in CISA's Known Exploited Vulnerabilities catalog, and the bulletin text I read does not say it was exploited. Patch anyway.
Sources
Last reviewed: 19 October 2026.
