Bug 1072419 (CVE-2014-0102) - CVE-2014-0102 kernel: security: keyring cycle detector DoS
Summary: CVE-2014-0102 kernel: security: keyring cycle detector DoS
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2014-0102
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: Red Hat1071346 1071396 Engineering1072425
Blocks: Embargoed1072464
TreeView+ depends on / blocked
 
Reported: 2014-03-04 14:42 UTC by Petr Matousek
Modified: 2021-02-17 06:48 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-04 14:52:48 UTC

Attachments (Terms of Use)
Upstream proposed patch (2.29 KB, patch)
2014-03-04 14:50 UTC, Petr Matousek 		no flags Details | Diff
View All

Description Petr Matousek 2014-03-04 14:42:31 UTC 
Description of the problem:
The problem is that search_nested_keyrings() sees two keyrings that have
matching type and description, so keyring_compare_object() returns true.
s_n_k() then passes the key to the iterator function -
keyring_detect_cycle_iterator() - which *should* check to see whether this is
the keyring of interest, not just one with the same name and, leads to
BUG_ON.

An unprivileged local user could use this flaw to crash the system. 

Introduced by:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b2a4df200d570b2c33a57e1ebfa5896e4bc81b69

References:
https://lkml.org/lkml/2014/2/27/507
Comment 1 Petr Matousek 2014-03-04 14:50:56 UTC 
Created attachment 870451 [details]
Upstream proposed patch
Comment 3 Petr Matousek 2014-03-04 14:52:48 UTC 
Statement:

This issue did not affect the versions of Linux kernel package as shipped with Red Hat Enterprise Linux 5, 6 and Red Hat Enterprise MRG 2 as they did not backport the commit that introduced this issue.
Comment 4 Petr Matousek 2014-03-04 16:58:21 UTC 
Upstream patch:

  http://www.kernelhub.org/?msg=425013&p=2
Note You need to log in before you can comment on or make changes to this bug.