Bug 1322755 (CVE-2016-3695) - CVE-2016-3695 kernel: Error injection via EINJ is allowed when securelevel is enabled
Summary: CVE-2016-3695 kernel: Error injection via EINJ is allowed when securelevel is...
Status: NEW
Alias: CVE-2016-3695
Product: Security Response
Classification: Other
Component: vulnerability   
(Show other bugs)
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=low,public=20160420,reported=2...
Keywords: Security
Depends On: 1321639 1329660 1329661
Blocks: 1322756
TreeView+ depends on / blocked
 
Reported: 2016-03-31 09:20 UTC by Adam Mariš
Modified: 2019-02-08 14:58 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Adam Mariš 2016-03-31 09:20:24 UTC
It was found that EINJ, error injection mechanism, is allowed even if securelevel, a prevention from userspace performing actions that undermine trust in the platform, is enabled. This can have undesirable side-effects, such as causing the platform to mark hardware as needing replacement.

Product bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1321639

Upstream patch:

https://github.com/mjg59/linux/commit/d7a6be58edc01b1c66ecd8fcc91236bfbce0a420

Comment 1 Adam Mariš 2016-03-31 09:20:39 UTC
Acknowledgments:

Name: Linn Crosetto (HP)

Comment 2 Adam Mariš 2016-04-20 12:25:07 UTC
Internal CVE assignment: CVE-2016-3695

Comment 5 Vladis Dronov 2016-04-22 14:32:43 UTC
Statement:

This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6 as the code with the flaw is not present in the products listed.

This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue.


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