CVE-2018-9519
UnknownEPSS 0.11%
Last modified
CVE-2018-9519 is a vulnerability of currently unknown severity. In easelcomm_hw_build_scatterlist, there is a possible out of bounds write due to a race condition. This could lead to local escalation of privilege with System privileges required. EPSS estimates a 0.11% chance of exploitation in the next 30 days.
Description
In easelcomm_hw_build_scatterlist, there is a possible out of bounds write due to a race condition. This could lead to local escalation of privilege with System privileges required. User interaction is not needed for exploitation. Product: Android. Versions: Android kernel. Android ID: A-69808833.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Android | All versions |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-9519?
In easelcomm_hw_build_scatterlist, there is a possible out of bounds write due to a race condition. This could lead to local escalation of privilege with System privileges required. User interaction is not needed for exploitation. Product: Android. Versions: Android kernel. Android ID: A-69808833.
How severe is CVE-2018-9519?
Severity scoring for CVE-2018-9519 is pending analysis. The EPSS model estimates a 0.11% probability of exploitation in the next 30 days.
How do I fix CVE-2018-9519?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2018
- CVE-2018-9513In copy_process of fork.c, there is possible memory corrupti…
- CVE-2018-9514In sdcardfs_open of file.c, there is a possible Use After Fr…
- CVE-2018-9515In sdcardfs_create and sdcardfs_mkdir of inode.c, there is a…
- CVE-2018-9516In hid_debug_events_read of drivers/hid/hid-debug.c, there i…
- CVE-2018-9517In pppol2tp_connect, there is possible memory corruption due…
- CVE-2018-9518In nfc_llcp_build_sdreq_tlv of llcp_commands.c, there is a p…
- CVE-2018-9521In parseMPEGCCData of NuPlayer2CCDecoder.cpp, there is a pos…
- CVE-2018-9522In the serialization functions of StatsLogEventWrapper.java,…
- CVE-2018-9523In Parcel.writeMapInternal of Parcel.java, there is a possib…
- CVE-2018-9524In functionality implemented in System UI, there are insuffi…
- CVE-2018-9525In the AndroidManifest.xml file defining the SliceBroadcastR…
- CVE-2018-9526In device configuration data, there is an improperly configu…
Are you affected by CVE-2018-9519?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
