CVE-2016-6604: Null Pointer Dereference

Published Jan 30, 2017

Updated

NULL pointer dereference in Samsung Exynos fimg2d driver for Android L(5.0/5.1) and M(6.0) allows attackers to have unspecified impact via unknown vectors. The Samsung ID is SVE-2016-6382.

Affected Software

18 affected components

Samsung Exynos fimg2d

Google Android=5.0

Google Android=5.0.1

Google Android=5.0.2

Google Android=5.1

Google Android=5.1.0

Google Android=5.1.1

Google Android=6.0

Google Android=6.0.1

All of the following

Samsung Exynos fimg2d

Any of the following

Google Android=5.0

Google Android=5.0.1

Google Android=5.0.2

Google Android=5.1

Google Android=5.1.0

Google Android=5.1.1

Google Android=6.0

Google Android=6.0.1

Event History

Jan 30, 2017

CVE Published

via MITRE·10:00 PM

Data Sourced

via MITRE·10:00 PM

Description

Data Sourced

via NVD·10:59 PM

DescriptionSeverityWeaknessAffected Software

Dec 13, 58332

Event

12:06 PM

Frequently Asked Questions

What is the severity of CVE-2016-6604?

The severity of CVE-2016-6604 is not explicitly stated but it can impact the stability and security of devices using vulnerable versions of the Samsung Exynos fimg2d driver.

How do I fix CVE-2016-6604?

To fix CVE-2016-6604, update the affected device to a patched version of the Samsung Exynos fimg2d driver.

Which devices are affected by CVE-2016-6604?

CVE-2016-6604 affects devices running Android L (5.0/5.1) and Android M (6.0) using the Samsung Exynos fimg2d driver.

What type of vulnerability is CVE-2016-6604?

CVE-2016-6604 is a NULL pointer dereference vulnerability within the Samsung Exynos fimg2d driver.

Can CVE-2016-6604 be exploited remotely?

The specific vectors for exploitation of CVE-2016-6604 are unspecified, so the ability for remote exploitation is unclear.