Bug 637675 - (CVE-2010-3432) CVE-2010-3432 kernel: sctp: do not reset the packet during sctp_packet_config
CVE-2010-3432 kernel: sctp: do not reset the packet during sctp_packet_config
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
public=20100915,source=lkml,reported=...
: Security
: 675997 (view as bug list)
Depends On: 637680 637681 637682 637863 637864 637865 637866 637867
Blocks:
  Show dependency treegraph
 
Reported: 2010-09-27 01:36 EDT by Eugene Teo (Security Response)
Modified: 2015-08-31 23:55 EDT (History)
20 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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 Eugene Teo (Security Response) 2010-09-27 01:36:25 EDT
Description of problem:
sctp_packet_config() is called when getting the packet ready for appending of chunks.  The function should not touch the current state, since it's possible to ping-pong between two transports when sending, and that can result packet corruption followed by skb overlfow crash.

Upstream commit:
http://git.kernel.org/linus/4bdab43323b459900578b200a4b8cf9713ac8fab

Reference:
http://marc.info/?l=linux-netdev&m=128453869227715&w=3
http://www.spinics.net/lists/linux-sctp/msg01051.html

Essentially, we are resetting the contents of the packet when it's not empty.
Comment 6 Eugene Teo (Security Response) 2010-09-29 05:09:54 EDT
Mitigation:

For users that do not run applications that use SCTP, you can prevent the sctp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file:

blacklist sctp

This way, the sctp module cannot be loaded accidentally, which may occur if an application that requires SCTP is started. A reboot is not necessary for this change to take effect.
Comment 7 Eugene Teo (Security Response) 2010-09-29 05:12:58 EDT
Statement:

This issue did not affect the version of Linux kernel as shipped with Red Hat Enterprise Linux 3 as it did not include support for SCTP. This was addressed in Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG via https://rhn.redhat.com/errata/RHSA-2010-0958.html and https://rhn.redhat.com/errata/RHSA-2010-0842.html. Future updates in Red Hat Enterprise Linux 4 and 5 may address this flaw.
Comment 8 Chuck Ebbert 2010-09-30 17:44:39 EDT
Fixed in 2.6.32.23 and 2.6.35.6
Comment 13 errata-xmlrpc 2010-11-10 14:08:27 EST
This issue has been addressed in following products:

  Red Hat Enterprise Linux 6

Via RHSA-2010:0842 https://rhn.redhat.com/errata/RHSA-2010-0842.html
Comment 14 errata-xmlrpc 2010-11-22 14:34:54 EST
This issue has been addressed in following products:

  Red Hat Enterprise Linux 6

Via RHSA-2010:0842 https://rhn.redhat.com/errata/RHSA-2010-0842.html
Comment 15 errata-xmlrpc 2010-12-01 17:24:26 EST
This issue has been addressed in following products:

  Red Hat Enterprise Linux 4

Via RHSA-2010:0936 https://rhn.redhat.com/errata/RHSA-2010-0936.html
Comment 16 errata-xmlrpc 2010-12-08 14:09:01 EST
This issue has been addressed in following products:

  MRG for RHEL-5

Via RHSA-2010:0958 https://rhn.redhat.com/errata/RHSA-2010-0958.html
Comment 21 errata-xmlrpc 2011-01-04 11:52:15 EST
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5

Via RHSA-2011:0004 https://rhn.redhat.com/errata/RHSA-2011-0004.html
Comment 22 Flavio Leitner 2011-07-11 15:26:33 EDT
*** Bug 675997 has been marked as a duplicate of this bug. ***

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