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 1141344 - (CVE-2014-3183) CVE-2014-3183 Kernel: HID: heap overflow due to lack of bounds checking
CVE-2014-3183 Kernel: HID: heap overflow due to lack of bounds checking
Status: CLOSED CURRENTRELEASE
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=20140821,repor...
: Security
Depends On: 1141347
Blocks: 1140968
  Show dependency treegraph
 
Reported: 2014-09-12 14:13 EDT by Prasad J Pandit
Modified: 2016-02-10 02:58 EST (History)
29 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-02-10 02:58:06 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 Prasad J Pandit 2014-09-12 14:13:40 EDT
Linux kernel built with the Human Interface Device(HID) Bus support(CONFIG_HID)
along with a driver for Logitech Unifying receivers full support
(CONFIG_LOGITECH_DJ), is vulnerable to an OOB write flaw. It could occur if a
device offers an HID report of arbitrary count value.

A local user with physical access to the system could use this flaw to crash
the system resulting in DoS or potentially, escalate their privileges on the
system.

Upstream fix:
-------------
  -> https://git.kernel.org/linus/51217e69697fba92a06e07e16f55c9a52d8e8945
Comment 1 Prasad J Pandit 2014-09-12 14:17:36 EDT
Statement:

This issue does not affect the versions of the kernel package as shipped with
Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2.
Comment 2 Prasad J Pandit 2014-09-12 14:18:23 EDT
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1141347]

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