How severe is CVE-2015-7891?

CVE-2015-7891 has a CVSS 3.x base score of 7.0, rated high severity. It is exploitable over local access with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2015-7891 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (47th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2015-7891?

CVE-2015-7891 primarily affects Samsung Samsung Mobile. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2015-7891?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2015-7891 published?

CVE-2015-7891 was published on 2017-08-02 and last updated on 2026-06-17.

CVE-2015-7891

CVE-2015-7891 is a high-severity vulnerability in Samsung Samsung Mobile with a CVSS 3.x base score of 7.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.

Key facts

Severity: High (CVSS 3.x base score 7.0)
CVSS v2: 4.4
EPSS exploit prediction: 1% (47th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-362
Affected product: Samsung Samsung Mobile
Published: 2017-08-02
Last modified: 2026-06-17

Description

Race condition in the ioctl implementation in the Samsung Graphics 2D driver (aka /dev/fimg2d) in Samsung devices with Android L(5.0/5.1) allows local users to trigger memory errors by leveraging definition of g2d_lock and g2d_unlock lock macros as no-ops, aka SVE-2015-4598.

Frequently asked questions

What is CVE-2015-7891?: Race condition in the ioctl implementation in the Samsung Graphics 2D driver (aka /dev/fimg2d) in Samsung devices with Android L(5.0/5.1) allows local users to trigger memory errors by leveraging definition of g2d_lock and g2d_unlock lock macros as no-ops, aka SVE-2015-4598.
How severe is CVE-2015-7891?: CVE-2015-7891 has a CVSS 3.x base score of 7.0, rated high severity. It is exploitable over local access with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2015-7891 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (47th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2015-7891?: CVE-2015-7891 primarily affects Samsung Samsung Mobile. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2015-7891?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2015-7891 published?: CVE-2015-7891 was published on 2017-08-02 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:o:samsung:samsung_mobile:5.0:*:*:*:*:*:*:*
cpe:2.3:o:samsung:samsung_mobile:5.1:*:*:*:*:*:*:*

More vulnerabilities in Samsung Samsung Mobile

CVE-2018-9143 — Critical (CVSS 9.8): On Samsung mobile devices with M(6.0) and N(7.x) software, a heap overflow in the sensorhub binder service leads to…
CVE-2018-9139 — Critical (CVSS 9.8): On Samsung mobile devices with N(7.x) software, a buffer overflow in the vision service allows code execution in a…
CVE-2017-5538 — Critical (CVSS 9.8): The kbase_dispatch function in arm/t7xx/r5p0/mali_kbase_core_linux.c in the GPU driver on Samsung devices with M(6.0)…
CVE-2016-9967 — Critical (CVSS 9.8): Lack of appropriate exception handling in some receivers of the Telecom application on Samsung Note devices with…
CVE-2016-9966 — Critical (CVSS 9.8): Lack of appropriate exception handling in some receivers of the Telecom application on Samsung Note devices with…
CVE-2016-9965 — Critical (CVSS 9.8): Lack of appropriate exception handling in some receivers of the Telecom application on Samsung Note devices with…

All CVEs affecting Samsung Samsung Mobile →

Other CWE-362 (Race Condition) vulnerabilities

CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…

Browse all CWE-362 (Race Condition) vulnerabilities →