Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1544482 - (CVE-2017-18174) CVE-2017-18174 kernel: Double free vulnerability in drivers/pinctrl/pinctrl-amd.c:amd_gpio_remove() function can lead to kernel panic
CVE-2017-18174 kernel: Double free vulnerability in drivers/pinctrl/pinctrl-a...
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=20180117,repor...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-12 10:58 EST by Adam Mariš
Modified: 2018-05-14 09:57 EDT (History)
45 users (show)

See Also:
Fixed In Version: kernel 4.7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-02-12 11:01:28 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)

  None (edit)
Description Adam Mariš 2018-02-12 10:58:04 EST
In the Linux kernel before 4.7, the amd_gpio_remove function in drivers/pinctrl/pinctrl-amd.c calls the pinctrl_unregister function, leading to a double free.

Introduced by:

https://github.com/torvalds/linux/commit/dbad75dd1f25e0107c643d42774a7f9a8ba85e9b

Fixed by:

https://github.com/torvalds/linux/commit/251e22abde21833b3d29577e4d8c7aaccd650eee

Re-introduced by (only in rc release):

https://github.com/torvalds/linux/commit/3bfd44306c65d073008b9ca8f062249f35576b61

Fixed again by:

https://github.com/torvalds/linux/commit/8dca4a41f1ad65043a78c2338d9725f859c8d2c3
Comment 1 Adam Mariš 2018-02-12 11:01:49 EST
Statement:

This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6 and 7, and Red Hat Enterprise MRG as they did not include the vulnerable code.

Note You need to log in before you can comment on or make changes to this bug.