Bug 1451685 (CVE-2017-1000363)
Summary: | CVE-2017-1000363 kernel: Out-of-bounds write in lp_setup in drivers/char/lp.c | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Adam Mariš <amaris> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | agordeev, aquini, bhu, dhoward, dominik.mierzejewski, dvlasenk, esammons, fhrbata, iboverma, jforbes, jkacur, jross, lgoncalv, lwang, matt, mcressma, mguzik, nmurray, pholasek, plougher, rvrbovsk, security-response-team, vdronov, williams |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
A vulnerability was found in the Linux kernel's lp_setup() function where it doesn't apply any bounds checking when passing "lp=none". This can result into overflow of the parport_nr[] array. An attacker with control over kernel command line can overwrite kernel code and data with fixed (0xff) values.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-07-25 12:18:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1456454, 1456493, 1456495, 1456496, 1456497, 1456499 | ||
Bug Blocks: | 1451686 |
Description
Adam Mariš
2017-05-17 09:54:18 UTC
Acknowledgments: Name: Roee Hay (HCL Technologies) Created kernel tracking bugs for this issue: Affects: fedora-all [bug 1456454] Statement: This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2, as the code with the flaw is not built and shipped with the products listed. Our kernels have CONFIG_PRINTER=m, this bug shouldn't be affecting us: the function we patch sits inside "#ifndef MODULE" block. This bug can only be triggered if someone recompiles the kernel with CONFIG_PRINTER=y, and then boots with "lp=none,none,none,none,none,none,none,none,none" (i.e. with more than 8 "none" parameters for lp=) on the kernel command line. I don't think this scenario is important for us. I propose WONTFIXing this. This was fixed for fedora with 4.12 rebases. |