In multiple locations, there is a possible way to bypass KASLR due to an unusual root cause.

published 2025-01-17 21 mo ago modified 2026-06-17 4 mo ago also EUVD-2018-20978

cvss: 4.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 0%
public exploits: 0; none known

In multiple locations, there is a possible way to bypass KASLR due to an unusual root cause. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.

Patch / fix

links 1

source.android.com/security/bulletin/pixel/2018-06-01 advisory

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 21 mo ago (2025-01-21)

Exploit prediction

0.10% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	4.4	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
CNA	3.1	4.4	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Affected products

Google Android

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

source.android.com /security/bulletin/pixel/2018-06-01
patch, vendor-advisory

Sources

CVE List CVE-2018-9384
NVD CVE-2018-9384

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary