Bug 238944 - CVE-2007-1592 IPv6 oops triggerable by any user
CVE-2007-1592 IPv6 oops triggerable by any user
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
5.0
All Linux
medium Severity high
: ---
: ---
Assigned To: Don Howard
Martin Jenner
impact=important,source=netdev,report...
: Security
: 238952 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-05-03 21:52 EDT by Marcel Holtmann
Modified: 2007-11-30 17:07 EST (History)
6 users (show)

See Also:
Fixed In Version: RHSA-2007-0347
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-05-16 14:57:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Marcel Holtmann 2007-05-03 21:52:47 EDT
Description of problem:

We accidently copy the ipv6 flow list to child sockets of listening
TCP sockets, but don't bump the reference count, clone the object,
etc.  And the list linkage of this object is not built such that
multiple sockets can point to it anyways.

Therefore if a listening socket has a flow list attached,
when a child connection closes we'll OOPS or double free
the flow list entry.

Any user can trigger this.


Version-Release number of selected component (if applicable):


How reproducible:
Writing a reproducer should be simple:

1) Open listening IPV6 TCP socket
2) Attach a flowlabel with IPV6_FLOWLABEL_MGR socket option,
   freq->flr_action == IPV6_FL_A_GET and appropriate metadata.
3) Connect to that listening socket, and close()

Steps to Reproduce:
1.
2.
3.
  
Actual results:

Instant oops.  The fix is to simply not inherit this ipv6
socket option.

Expected results:


Additional info:

This was discovered and merged upstream right before this
past weekend.  See:

	http://marc.info/?l=linux-netdev&m=117406721731891&w=2

Can someone help me audit RHEL3 and RHEL4 to make sure we
get those fixed up if necessary?  I'm about to go away for
3 days.
Comment 1 Don Howard 2007-05-07 13:16:12 EDT
A patch for this issue has been included in build 2.6.18-8.1.4.el5.
Comment 2 Mike Gahagan 2007-05-09 17:24:31 EDT
Confirmed that fix is in 2.6.18-8.1.4.el5.

Comment 4 Don Howard 2007-05-11 18:08:32 EDT
*** Bug 238952 has been marked as a duplicate of this bug. ***
Comment 6 Red Hat Bugzilla 2007-05-16 14:57:26 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2007-0347.html

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