Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1396670 - (CVE-2016-9278) CVE-2016-9278 kernel: Kernel Crash on /dev/fimg2d ioctl command
CVE-2016-9278 kernel: Kernel Crash on /dev/fimg2d ioctl command
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20161109,repor...
: Security
Depends On: 1396671
Blocks: 1394822
  Show dependency tree / graph
 
Reported: 2016-11-18 17:42 EST by Adam Mariš
Modified: 2016-11-28 00:47 EST (History)
34 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-28 00:47:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Adam Mariš 2016-11-18 17:42:21 EST 
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 17:43:56 EST 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1396671]
Comment 2 Justin M. Forbes 2016-11-21 12:43:45 EST 
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 00:47:11 EST 
Righto, will close that up.  There was enough CONFIG_EXYNO in the fedora kernels that it was affected.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.