Bug 165663 - ipvs overflow
ipvs overflow
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Miller
Brian Brock
: 165664 165665 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2005-08-11 05:27 EDT by Mark J. Cox (Product Security)
Modified: 2012-06-20 09:25 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 09:25:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mark J. Cox (Product Security) 2005-08-11 05:27:25 EDT
Some ipvs overflows were found and fixed in 2.4 (20050531) and later forward
ported to 2.6 (20050626)

"The impact of the bugs is a kernel stack overflow and privilege escalation
ioctls.  People running with 'root=all caps' (i.e., most users) are not
really affected (there's nothing to escalate), but SELinux and similar
users should take it seriously if they grant CAP_NET_ADMIN to other users."

Patch and details:


We should fix this for RHEL4
Comment 3 James Morris 2005-08-11 12:12:26 EDT
SELinux does not grant capabilities to users.
Comment 4 Stephen Smalley 2005-11-15 05:54:26 EST
Correct - SELinux is presently restrictive only (i.e. only further restricts
access); use of a capability aka privilege still requires uid 0 (at least
initially) plus the corresponding SELinux permission.
Comment 5 Mark J. Cox (Product Security) 2005-11-15 06:28:28 EST
thanks; removing security tag
Comment 6 Jiri Pallich 2012-06-20 09:25:47 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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