-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                        ESB-2008.0565 -- [Solaris]
On Systems Running Solaris Cluster 3.2, "scdpmd" May Leak Memory and Render
   the System Unusable When "reboot_on_path_failure" Property is Enabled
                                2 June 2008

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:              Solaris Cluster 3.2
Publisher:            Sun Microsystems
Operating System:     Solaris
Impact:               Denial of Service
Access:               Existing Account

Original Bulletin:    
  http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-66-201254-1

- --------------------------BEGIN INCLUDED TEXT--------------------

   Solution Type: Sun Alert
   Solution  201254 :   On Systems Running Solaris Cluster 3.2, "scdpmd"
   May Leak Memory and Render the System Unusable When
   "reboot_on_path_failure" Property is Enabled          
   Previously Published As: 103120

   Bug ID: 6563949

   Product
   Solaris Cluster 3.2

   Date of Workaround Release: 18-OCT-2007

   Date of Resolved Release: 30-May-2008

   SA Document Body
   Solaris Cluster 3.2 with certain patches may become low on memory (see 
   below for details)

   1. Impact

   Systems running Solaris Cluster 3.2, with the patches listed in the
   "Contributing Factors" section below installed, may become extremely
   low on memory causing other processes running on the system to be
   affected. It may also be possible that "scdpmd" will dump core when it
   can't allocate memory.
   2. Contributing Factors

   This issue can occur in the following releases:

   SPARC Platform
     * Solaris Cluster 3.2 (for Solaris 9) with patch 125510-01 or later
       and without patch 126105-04
     * Solaris Cluster 3.2 (for Solaris 10) with patch 125511-01 or later
       and without patch 126106-04

   x86 Platform
     * Solaris Cluster 3.2 (for Solaris 10) with patch 125512-01 or later
       and without patch 126107-04

   Note 1: Sun Cluster 3.0 and 3.1 are not affected by this issue.

   Note 2: Sun Cluster 3.2 is not supported on the Solaris 9 x86
   platform.

   The described issue only occurs if "reboot_on_path_failure" is
   enabled. To verify if "reboot_on_path_failure" is enabled on a system,
   the following command can be used:
    # clnode show -p reboot_on_path_failure
    Cluster Nodes ===
    Node Name:                       phys-foo-1
    reboot_on_path_failure: enabled
    Node Name:                       phys-foo-2
    reboot_on_path_failure:          enabled

   3. Symptoms

   Should the described issue occur, the size value in ps (SZ) for
   "scdpm" will increase over time:
    ps -el|egrep 'PID|scdpmd'
    F S    UID   PID  PPID   C PRI NI     ADDR     SZ    WCHAN TTY      TIME CMD
    0 S      0  1107     1   0  40 20       ?     2125        ? ?       27:28 scdpmd

   After all the memory is consumed, "scdpmd" dumps core with a stack
   trace similar to the following:
   <start>
    libc.so.1`_lwp_kill+8(6, 0, ff0ee390, ff125080, ffffffff, 6)
    libc.so.1`abort+0x110(ff13b140, 1, ff124eac, aa1a0, ff0ed2d8, 0)
    libCrun.so.1`void __Cimpl::default_terminate+4(ff13f198, 0, ff13f178, 
    153bc, ff13a810, ff12507c)
    libCrun.so.1`void __Cimpl::ex_terminate+0x2c(ff13b140, 0, 0, ff13b140, 
    ff13a810, 1)
    0xff125b90(ff13b140, 0, 0, 14d08, ff13a810, 0)
    libCrun.so.1`void __Crun::ex_chk_unexpected+0xa8(ff13aef4, ff1270d0, 
    ff13aef8, 14e48, 14964, 0)
    libCrun.so.1`void*operator new+0x98(464, ff13b028, ff13b190, 137d4, 
    ff13a810, 0)
    libclcomm.so.1`Buf*MarshalStream::newbuf+0x3c(5400, 462, 1ca724, 
    fe2fbbe8, fefb7a84, fdd520e0)
    libclcomm.so.1`unsigned MarshalStream::alloc_chunk+0x34(fdd520b0, 10, 
    50, 2, 200, 0)
    libclcomm.so.1`sdoor_sendstream::sdoor_sendstream #Nvariant 1+0x94
    (fdd52070, fe2fba18, 5400, fe2fbbe8, ff13a810, fefb7a84)
    libclcomm.so.1`sendstream*sdoor_transport::reserve_resources+0x20
    (fe2fba18, fe2fba18, 0, fefcbdc4, 651c, fdd52070)
    libclcomm.so.1`CORBA::ExceptionStatus remote_handler::invoke_twoway+
    0x144(fdd52130, fefd2fdc, fe2fbb60, fefcb478, fefcbfc8, fe2fbbe8)
    libclcomm.so.1`CORBA::ExceptionStatus remote_handler::invoke+0x58
    (fdd52130, fefd2fdc, fe2fbb60, fefcbfc8, fe2fbbe8, fdeea988)
    libclcomm.so.1`void ccr::readonly_table_stub::next_element+0xa4(fdd51910, 
    fe2fbbd4, fe2fbbe8, fee1424c, fee1427c, fedf093c)
    0xfdecdb24(666870, fe2fbc7c, fe2fbbe0, ff2f6d18, fdd51910, fdeea988)
    libdid_ccr.so.1`did_impl_getinstlist+0xa4(fe2fbd44, 0, 666870, 1b8a8, 
    ff2b6568, fdeea988)
    libdid.so.1`did_getinstlist+0xac(fe2fbd44, 0, 666870, 0, ff2cd634, 18998)
    libdid.so.1`map_to_did_device+0xa8(fdcc5426, 0, fdcc5425, 17170, 0, 
    2f000000)
    0x13520(fdca9b18, fdc20df0, 3, 0, 0, fdc20df0)
    0x13170(4f098, fdca9b18, 24b08, 13904, 24c00, 24800)
    0x13938(4f098, 4e7f0, 46b4b6f4, 4f8a0, 4, fe2fbf8c)
    libc.so.1`_lwp_start(0, 0, 0, 0, 0, 0)
    <end>

   4. Workaround

   To work around this issue, disable "reboot_on_path_failure" property
   by using the following command:
    # clnode set -p reboot_on_path_failure=disabled phys-foo-1

   5. Resolution

   This issue is addressed in the following releases:

   SPARC Platform
     * Solaris Cluster 3.2 (for Solaris 9) with patch 126105-04 or later
     * Solaris Cluster 3.2 (for Solaris 10) with patch 126106-04 or later

   x86 Platform
     * Solaris Cluster 3.2 (for Solaris 10) with patch 126107-04 or later

   This Sun Alert notification is being provided to you on an "AS IS"
   basis. This Sun Alert notification may contain information provided by
   third parties. The issues described in this Sun Alert notification may
   or may not impact your system(s). Sun makes no representations,
   warranties, or guarantees as to the information contained herein. ANY
   AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION
   WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
   NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT
   YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT,
   INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE
   OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN.
   This Sun Alert notification contains Sun proprietary and confidential
   information. It is being provided to you pursuant to the provisions of
   your agreement to purchase services from Sun, or, if you do not have
   such an agreement, the Sun.com Terms of Use. This Sun Alert
   notification may only be used for the purposes contemplated by these
   agreements.
   Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa
   Clara, CA 95054 U.S.A. All rights reserved

- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:

        http://www.auscert.org.au/render.html?cid=1980

If you believe that your computer system has been compromised or attacked in 
any way, we encourage you to let us know by completing the secure National IT 
Incident Reporting Form at:

        http://www.auscert.org.au/render.html?it=3192

===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
===========================================================================

-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967

iQCVAwUBSENryih9+71yA2DNAQLZdgP+M29JDvhHt644QEOWjtcp3FFAnikKOCEe
FLNQi4myGfHrEZinH7B02DD7bfhwFlMJuVa2aB1z8v2O5WkusLeIpmVD4QaQprKd
hPTEVx9bN0tMvHQSzcE54scs0KzsC2lpHZsEHQce7yngd37RLvm6w/QML79IUcXh
2Tq8zl+WQ54=
=bCHE
-----END PGP SIGNATURE-----