Bug 1396670 (CVE-2016-9278)

Summary:	CVE-2016-9278 kernel: Kernel Crash on /dev/fimg2d ioctl command
Product:	[Other] Security Response	Reporter:	Adam Mariš <amaris>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	agordeev, aquini, arm-mgr, bhu, dhoward, esammons, fhrbata, gansalmon, iboverma, ichavero, itamar, jforbes, jkacur, joelsmith, jonathan, jross, jwboyer, kernel-maint, kernel-mgr, labbott, lgoncalv, lwang, madhu.chinakonda, matt, mchehab, mcressma, mguzik, nmurray, pholasek, plougher, rt-maint, rvrbovsk, williams, wmealing
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-28 05:47:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1396671
Bug Blocks:	1394822

Description Adam Mariš 2016-11-18 22:42:21 UTC

The fimg2d which is one of the graphic devices for Exynos chipsets doesn’t have exception control routines to handle unexpected commands and it can lead to kernel panic. The patch prevents kernel panic by ignoring inappropriate commands at the state.

CVE assignment:

http://seclists.org/oss-sec/2016/q4/405

External References:

http://security.samsungmobile.com/smrupdate.html#SMR-NOV-2016

Comment 1 Adam Mariš 2016-11-18 22:43:56 UTC

Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1396671]

Comment 2 Justin M. Forbes 2016-11-21 17:43:45 UTC

Not sure why we have a bug on this, the driver in question is in an upstream android tree at google, but not in Linus' linux kernel tree. Fedora doesn't ship this driver.

Comment 3 Wade Mealing 2016-11-28 05:47:11 UTC

Righto, will close that up.  There was enough CONFIG_EXYNO in the fedora kernels that it was affected.