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 1500094 - (CVE-2017-5123) CVE-2017-5123 kernel: Missing access_ok() checks in waitid()
CVE-2017-5123 kernel: Missing access_ok() checks in waitid()
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
impact=important,public=20171012,repo...
: Security
Depends On: 1501762
Blocks: 1500095
  Show dependency tree / graph
 
Reported: 2017-10-09 16:53 EDT by Adam Mariš
Modified: 2017-10-25 19:14 EDT (History)
48 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
The waitid implementation in upstream kernels did not restrict the target destination to copy information results. This can allow local users to write to otherwise protected kernel memory, which can lead to privilege escalation.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-10-13 11:30:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Proposed patch (1.21 KB, patch)
2017-10-09 16:55 EDT, Adam Mariš 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Adam Mariš 2017-10-09 16:53:50 EDT 
A flaw was found in the upstream version of the kernels implementation of waitid systemcall.   This flaw was the removal of validation of the target location where the kernel would copy the results.   Previously it would implement a check to restrict the results to be copied to a valid userspace address, a new patch had inadvertently allowed copying to kernel addresses.

An attacker could use this flaw to corrupt memory, panic the machine or possibly allow for arbitary memory writes.
Comment 1 Adam Mariš 2017-10-09 16:53:53 EDT 
Acknowledgments:

Name: Chris Salls
Comment 2 Adam Mariš 2017-10-09 16:55 EDT 
Created attachment 1336563 [details]
Proposed patch
Comment 4 Andrej Nemec 2017-10-13 03:12:44 EDT 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1501762]
Comment 5 Andrej Nemec 2017-10-13 03:13:48 EDT 
References:

http://seclists.org/oss-sec/2017/q4/78
Comment 6 Andrej Nemec 2017-10-13 11:09:00 EDT 
Statement:

This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux as they did not include the upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4c48abe91be03d191d0c20cc755877da2cb35622 that introduced this issue.
Comment 8 Fedora Update System 2017-10-24 01:29:22 EDT 
kernel-4.13.8-300.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
Comment 9 Fedora Update System 2017-10-25 17:21:28 EDT 
kernel-4.13.8-100.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
Comment 10 Fedora Update System 2017-10-25 19:14:18 EDT 
kernel-4.13.8-200.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
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.