PROBLEM: (QAR 52115) (Patch ID: OSF415-405080) ******** An application running System V using psuedoterminals may hang if it opens the slave side before the master is open. If the slave side of a System V master psuedoterminal is opened before it is unlocked on the master side via unlockpt(), the calling process will block forever on the open() even after the unlockpt() has been issued and the lock flag lifted from the device. Once the out of sequence race condition occurs, the slave device cannot be opened again by any process until the original hung process is terminated. PROBLEM: (SSRT0476U, QAR 53372) (Patch ID: OSF415-405128) ******** A potential security vulnerability has been discovered, where under certain circumstances, a kernel memory fault panic may occur. Digital has corrected this potential vulnerability. The kernel memory fault panic will have a stack trace of the panic'ing process as follows: 1 panic(s = 0xfffffc00006a13e0 = "kernel memory fault") 2 trap() 3 _XentMM() 4 putq_owned 5 putq 6 pts_wput 7 csq_lateral 8 puthere 9 ldtty_wput 10 csq_turnover 11 osr_pop_subr 12 osr_close_subr 13 pse_close 14 speclose 15 clearalias 16 exit 17 rexit 18 syscall 19 _Xsyscall PROBLEM: (CLD ADP-05797) (Patch ID: OSF415-410147) ******** A call to the select() system call may hang or incorrectly indicate that there is a message waiting from a terminal when there is nothing there. PROBLEM: (QAR 63014, QAR 62791) (Patch ID: OSF415-405436) ******** This patch fixes a problem in which the system may panic with the following error message "kernel memory fault". An example panic stack trace might look like: > 0 boot 1 panic 2 trap 3 _XentMM 4 rmvq 5 pts_wput 6 csq_lateral 7 puthere 8 ldtty_bsd43_ioctl 9 ldtty_ioctl 10 ldtty_wput 11 csq_lateral 12 puthere 13 osr_str 14 osr_run 15 pse_ioctl 16 spec_ioctl 17 vn_ioctl 18 ioctl_base 19 ioctl 20 syscall 21 _Xsyscall