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

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

                        ESB-2008.0616 -- [Solaris]
         Installing Solaris 10 Fibre Channel Device Driver patches
           without an immediate reboot may cause a System Panic
                               13 June 2008

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

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

Product:              Solaris 10
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-238630-1

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

   Solution Type: Sun Alert
   Solution  238630 :   Installing Solaris 10 Fibre Channel Device Driver
   patches without an immediate reboot may cause a System Panic          
   Bug ID: 6704883

   Product
   Solaris 10 Operating System

   Date of Workaround Release: 11-Jun-2008

   SA Document Body

   Installing Solaris 10 Fibre Channel Device Driver patches without an 
   immediate reboot may cause a System Panic

   1. Impact

   Installing certain Solaris 10 Fibre Channel Device Drivers patches (as
   listed below in section 2) may cause a system to panic if installation
   of those patches is followed by the installation of certain CD-ROM
   Install Boot Image patches without an intervening reboot.

   2. Contributing Factors

   This issue can occur in the following releases:
   SPARC Platform:
     * Solaris 10 with patch 125184-05 (or later) and with patch
       119081-25 (or later)

   x86 Platform:
     * Solaris 10 with patch 125185-05 (or later) and with patch
       119082-25 (or later)

   For SPARC platforms, this occurs when doing the following:
   By first installing patch 125184-05 or later (Solaris 10 Fibre Channel
   Device Driver) followed by patch 119081-25 or later (Solaris 10 CD-ROM
   Install Boot Image Patch) without a reboot between patch
   installations.

   For x86 platforms, this occurs when doing the following:
   By first installing patch 125185-05 or later (Solaris 10 Fibre Channel
   Device Driver) followed by patch 119082-25 or later (SunOS 5.10 CD-ROM
   Install Boot Image Patch) without a reboot between patch
   installations.

   Notes:
    1. Solaris 8 and 9 and OpenSolaris are not impacted by this issue.
    2. This condition has been seen to occur when installing the SPARC
       recommended patch clusters dated prior to 06-June-2008.
    3. This issue has not been seen in the x86 clusters which do not have
       the patch installation order which triggers this issue.
    4. This issue has not been seen in the Sun Alert clusters which
       include the Sun Fibre Channel Device Drivers patch at a revision
       lower than -05.
    5. The panic occurs as a result of the inconsistent fcip(7D) and
       fctl(7D) modules loaded in memory.
    6. This issue only occurs when installing the two patches one after
       the other in the stated order (Drivers patch first, followed by
       the CD-ROM Install Boot Image patch) without a reboot in between
       the two.

   3. Symptoms

   There are no predictable symptoms that would indicate the system will
   panic prior to patch installation. If the CD-ROM Install Boot Image
   Patch is installed after the Sun Fibre Channel Device Drivers patch
   without an intervening reboot, the system will panic during or
   immediately after installation of the CD-ROM Install Boot Image patch.

   4. Workaround

   To avoid this issue, install the patches in the correct order, with
   the CD-ROM Install Boot Image Patch installed first, followed by a
   reboot, before the Sun Fibre Channel Device Drivers patch is
   installed.

   If the described issue has already occurred, rebooting the system will
   restore normal operation. The inconsistency that caused the panic will
   have been resolved by the reboot.

   5. Resolution

   A final resoution is pending completion.

   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

iQCVAwUBSFHsKih9+71yA2DNAQJcfQP/eyZPrCmoFSvrv/02iVlUWnbDdY4kGzdc
j4AI7Ig+qRMblrlvlXlUcRGmlsrfmoZ199V3hsnmWKQ+3cs17snJzxU4Yj+Kt4ZK
aCIYIALTVY5mm3hmNs/FUabzO1YW7Ue2WUKSD5mBVeq+xPjkAU1ZiP9uD49if5fk
Eg1ev2OrSpY=
=BFLj
-----END PGP SIGNATURE-----