Bug 1489078 (CVE-2017-12146) - CVE-2017-12146 kernel: Race condition in driver_override implementation
Summary: CVE-2017-12146 kernel: Race condition in driver_override implementation
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2017-12146
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1489079 1494199
Blocks: 1489083
TreeView+ depends on / blocked
 
Reported: 2017-09-06 16:10 UTC by Adam Mariš
Modified: 2021-02-17 01:36 UTC (History)
48 users (show)

Fixed In Version: kernel 4.13
Doc Type: Bug Fix
Doc Text:
It was found that the driver_override implementation in base/platform.c in the Linux kernel is susceptible to race condition when different threads are reading vs storing a different driver override.
Clone Of:
Environment:
Last Closed: 2017-09-21 16:25:35 UTC
Embargoed:

Attachments (Terms of Use)

Description Adam Mariš 2017-09-06 16:10:26 UTC 
It was found that the driver_override implementation in base/platform.c is susceptible to race condition when different threads are reading vs storing a different driver override.

Upstream patch:

https://github.com/torvalds/linux/commit/6265539776a0810b7ce6398c27866ddb9c6bd154

Introduced by commit:

https://github.com/torvalds/linux/commit/3d713e0e382e
Comment 1 Adam Mariš 2017-09-06 16:11:48 UTC 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1489079]
Comment 2 Adam Mariš 2017-09-06 16:48:17 UTC 
External References:

https://source.android.com/security/bulletin/2017-09-01
Comment 3 Justin M. Forbes 2017-09-06 18:06:05 UTC 
This was fixed in the 4.12.1 stable release and is on all currently supported Fedora releases.
Comment 7 Vladis Dronov 2017-09-21 16:24:09 UTC 
Statement:

This issue does not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2 as the code with the flaw is not present in the products listed.
Note You need to log in before you can comment on or make changes to this bug.