CVE-2017-5538
First published: Thu Mar 23 2017(Updated: )
The kbase_dispatch function in arm/t7xx/r5p0/mali_kbase_core_linux.c in the GPU driver on Samsung devices with M(6.0) and N(7.0) software and Exynos AP chipsets allows attackers to have unspecified impact via unknown vectors, which trigger an out-of-bounds read, aka SVE-2016-6362.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Samsung Mobile | =6.0 | |
| Samsung Mobile | =7.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-5538?
The severity of CVE-2017-5538 is considered high due to the potential for an out-of-bounds read that can be exploited.
How do I fix CVE-2017-5538?
To mitigate CVE-2017-5538, ensure that your Samsung device is updated to the latest software version offered by Samsung.
What devices are affected by CVE-2017-5538?
CVE-2017-5538 affects Samsung devices running the M(6.0) and N(7.0) versions of the Samsung Mobile software.
What are the potential impacts of CVE-2017-5538?
The potential impacts of CVE-2017-5538 include unspecified vulnerabilities that could be triggered via unknown vectors.
Is there a workaround for CVE-2017-5538?
Currently, the best workaround for CVE-2017-5538 is to ensure that devices are updated and patched as recommended by Samsung.
- agent/references
- agent/tags
- agent/type
- agent/remedy
- agent/first-publish-date
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/last-modified-date
- agent/severity
- agent/weakness
- agent/author
- agent/softwarecombine
- agent/description
- agent/event
- vendor/samsung
- canonical/samsung mobile
- version/samsung mobile/6.0
- version/samsung mobile/7.0