Bug 815188 (CVE-2012-2127)

Summary:	CVE-2012-2127 kernel: pid namespace leak in kernel 3.0 and 3.1
Product:	[Other] Security Response	Reporter:	Eugene Teo (Security Response) <eteo>
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, anton, arozansk, bhu, davej, dhoward, fhrbata, gansalmon, itamar, jforbes, jkacur, jonathan, jwboyer, kernel-maint, kernel-mgr, lgoncalv, lwang, madhu.chinakonda, plougher, pmatouse, rt-maint, sforsber, vgoyal, williams
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-08-24 12:59:42 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:	815191, 815192
Bug Blocks:	815184

Description Eugene Teo (Security Response) 2012-04-23 04:37:34 UTC

Vadim Ponomarev (ccrssaa at karelia.ru),  report a pid
namespace leak caused by vsftpd.

Detailed discussion can be found in:
https://bugzilla.novell.com/show_bug.cgi?id=757783

Introduced by:
http://git.kernel.org/linus/423e0ab086ad8b33626e45fa94ac7613146b7ffa

Upstream commit:
http://git.kernel.org/linus/905ad269c55fc62bee3da29f7b1d1efeba8aa1e1

Steps to reproduce:
https://bugzilla.novell.com/show_bug.cgi?id=757783#c0

Acknowledgements:

Red Hat would like to thank Vadim Ponomarev for reporting this issue.

Comment 3 Eugene Teo (Security Response) 2012-04-23 05:09:46 UTC

Created kernel tracking bugs for this issue

Affects: fedora-all [bug 815192]

Comment 4 Eugene Teo (Security Response) 2012-04-23 05:25:09 UTC

Statement:

This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4, 5, and 6 as they did not backport the upstream commit 423e0ab0 that introduced this issue. This issue did not affect Red Hat Enteprise Linux MRG 2.