CVE-2018-11818: google android Race Condition
CVSS: 7.0v3.0HighModified
Published 18-09-2018Last modified 05-08-2024
Vulnerability summary
CVE-2018-11818 is a high (CVSS 7.0) Race Condition vulnerability in google android. EPSS estimates a 0.14% chance of exploitation in the next 30 days, higher than 2.8% of scored vulnerabilities.
CVSS score
7.0/10
010
High · v3.0 (NVD)EPSS score
0.14%
0%100%
Low · 0.00 pp in 30 daysKEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded
Timeline
- 18-09-2018PublishedVulnerability first disclosed.
- 05-08-2024Last modifiedVulnerability information updated.
Description
In all android releases (Android for MSM, Firefox OS for MSM, QRD Android) from CAF using the linux kernel, LUT configuration is passed down to driver from userspace via ioctl. Simultaneous update from userspace while kernel drivers are updating LUT registers can lead to race condition.
CVSS metrics
2 scores · 1 source · 2 versionsHigh 7.0Preferred score · NVD (NIST)
CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HSourcesSingle source
Medium 4.4Preferred score · NVD (NIST)
AV:L/AC:M/Au:N/C:P/I:P/A:PSourcesSingle source
EPSS trend
Probability
0.14%
Chance of exploitation in the next 30 days
Percentile
3%
Versus all other CVEs
30-day change
0.00 pp
From 0.14% on 19-09-2026
19-09-202619-10-2026
EPSS score0.14%
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root cause- CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
- CWE-416Use After FreeThe product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Affected systems
Google1 product
- androidna
Qualcomm, inc.1 product
- android for msm, firefox os for msm, qrd androidAll Android releases from CAF using the Linux kernel
2 vendors · 2 products
References
3 links- www.codeaurora.org/security-bulletin/2018/09/04/september-2018-code-aurora-security-bulletinX Refsource CONFIRMPatchThird Party Advisory
- source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=7d1e40be0f7da526f1109005383aa55f5646fc13X Refsource CONFIRMPatchThird Party Advisory
- source.codeaurora.org/quic/la/kernel/msm-4.4/commit/?id=999bfde119d881a09218eb045d41fb83e67f0d10X Refsource CONFIRMPatchThird Party Advisory