Overly broad permissions can turn one compromised account into a much larger security problem. Learn how to reduce unnecessary access, review privileges, and apply least privilege across modern Linux systems. Review Linux Privileges×
Stay Secure with the Latest Linux Advisories
Refine advisories
X Clear Filters
Get the latest News and Insights
Get the latest Linux and open source security news straight to your inbox.
Community Poll
Should Linux servers automatically install security updates?
Loading...
Explore Latest Linux Security advisories
We found 0 articles for you...
217
security advisorysecurity updatecriticalOracle Linux 9 ELSA-2023-5094 Important: QEMU Remote Denial of Service
The following updated rpms for Oracle Linux 9 have been uploaded to the Unbreakable Linux Network: . Oracle Linux Security Advisory ELSA-2023-5094 https://linux.oracle.com/errata/ELSA-2023-5094.html The following updated rpms for Oracle Linux 9 have been uploaded to the Unbreakable Linux Network: x86_64: qemu-guest-agent-7.2.0-14.el9_2.5.x86_64.rpm qemu-img-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-audio-pa-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-block-curl-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-block-rbd-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-common-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-core-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-device-display-virtio-gpu-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-device-display-virtio-gpu-pci-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-device-display-virtio-vga-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-device-usb-host-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-device-usb-redirect-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-docs-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-tools-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-ui-egl-headless-7.2.0-14.el9_2.5.x86_64.rpm qemu-kvm-ui-opengl-7.2.0-14.el9_2.5.x86_64.rpm qemu-pr-helper-7.2.0-14.el9_2.5.x86_64.rpm aarch64: qemu-guest-agent-7.2.0-14.el9_2.5.aarch64.rpm qemu-img-7.2.0-14.el9_2.5.aarch64.rpm qemu-kvm-7.2.0-14.el9_2.5.aarch64.rpm qemu-kvm-audio-pa-7.2.0-14.el9_2.5.aarch64.rpm qemu-kvm-block-curl-7.2.0-14.el9_2.5.aarch64.rpm qemu-kvm-block-rbd-7.2.0-14.el9_2.5.aarch64.rpm qemu-kvm-common-7.2.0-14.el9_2.5.aarch64.rpm qemu-kvm-core-7.2.0-14.el9_2.5.aarch64.rpm qemu-kvm-device-display-virtio-gpu-7.2.0-14.el9_2.5.aarch64.rpm qemu-kvm-device-display-virtio-gpu-pci-7.2.0-14.el9_2.5.aarch64.rpm qemu-kvm-device-usb-host-7.2.0-14.el9_2.5.aarch64.rpm qemu-kvm-docs-7.2.0-14.el9_2.5.aarch64.rpm qemu-kvm-tools-7.2.0-14.el9_2.5.aarch64.rpm qemu-pr-helper-7.2.0-14.el9_2.5.aarch64.rpm SRPMS: https://oss.oracle.com:443/ol9/SRPMS-updates//qemu-kvm-7.2.0-14.el9_2.5.src.rpm Related CVEs: CVE-2023-3354 Description of changes: [7.2.0-14.el9_2.5] - rhelguest failed boot with multi disks on error Failed to start udev Wait for Complete Device Initialization - CVE-2023-3354 QEMU: VNC: improper I/O watch removal in TLS handshake can lead to remote unauthenticated denial of service - hotplug/hotunplug mlx vdpa device to the occupied addr port, then qemu core dump occurs after shutdown guest _______________________________________________ El-errata mailing list
Sep 14, 2023
•Important
Oracle
203
security advisorymemory corruptionarbitrary codeMageia 7: 2020-0395 Moderate: Firefox Memory Corruption Attack
Mozilla developers and community members Jason Kratzer, Simon Giesecke, Philipp, and Christian Holler reported memory safety bugs present in Firefox ESR 78.3. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code (CVE-2020-15683). . MGASA-2020-0395 - Updated nss and firefox packages fix security vulnerabilities Publication date: 24 Oct 2020 URL: https://advisories.mageia.org/MGASA-2020-0395.html Type: security Affected Mageia releases: 7 CVE: CVE-2020-15683, CVE-2020-15969, CVE-2020-25648 Mozilla developers and community members Jason Kratzer, Simon Giesecke, Philipp, and Christian Holler reported memory safety bugs present in Firefox ESR 78.3. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code (CVE-2020-15683). A use-after-free bug in the usersctp library was reported upstream. We assume this could have led to memory corruption and a potentially exploitable crash (CVE-2020-15969). A flaw was found in the way NSS handled CCS (ChangeCipherSpec) messages in TLS 1.3. This flaw allows a remote attacker to send multiple CCS messages, causing a denial of service for servers compiled with the NSS library. The highest threat from this vulnerability is to system availability. This flaw affects NSS versions before 3.58 (CVE-2020-25648). References: - https://bugs.mageia.org/show_bug.cgi?id=27460 - - https://www.mozilla.org/en-US/security/advisories/mfsa2020-46/ - https://access.redhat.com/errata/RHSA-2020:4310 - https://www.cve.org/CVERecord?id=CVE-2020-15683 - https://www.cve.org/CVERecord?id=CVE-2020-15969 - https://www.cve.org/CVERecord?id=CVE-2020-25648 SRPMS: - 7/core/rootcerts-20201021.00-1.mga7 - 7/core/nss-3.58.0-1.mga7 - 7/core/firefox-78.4.0-1.mga7 - 7/core/firefox-l10n-78.4.0-1.mga7 . Patch note MGASA-2020-0395 for Firefox and NSS addresses vulnerabilities linked to memory safety,potentially enabling malicious activities.. Mozilla Firefox Issues, NSS Security Flaws, Memory Safety Exploits. . LinuxSecurity.com Team
Oct 24, 2020
Mageia
100
security advisorysecurity issuekernel updateSUSE SLES 9: 2010-036 Moderate: Kernel Remote Denial Of Service
This update fixes various security issues and some bugs in the SUSE Linux This update fixes various security issues and some bugs in the SUSE Linux Enterprise 9 kernel. Enterprise 9 kernel. Following security issues were fixed: CVE-2010-2521: A crafted NFS write request might have caused a buffer overwrite, potentially causing a kernel crash.. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: kernel Announcement ID: SUSE-SA:2010:036 Date: Wed, 01 Sep 2010 11:00:00 +0000 Affected Products: SUSE SLES 9 Open Enterprise Server Novell Linux POS 9 Vulnerability Type: remote denial of service CVSS v2 Base Score: 7.8 (AV:N/AC:L/Au:N/C:N/I:N/A:C) SUSE Default Package: yes Cross-References: CVE-2007-6206, CVE-2007-6733, CVE-2008-0598 CVE-2008-3275, CVE-2009-1389, CVE-2009-4020 CVE-2009-4537, CVE-2010-0727, CVE-2010-1083 CVE-2010-1088, CVE-2010-1188, CVE-2010-2521 Content of This Advisory: 1) Security Vulnerability Resolved: Linux kernel security update Problem Description 2) Solution or Work-Around 3) Special Instructions and Notes 4) Package Location and Checksums 5) Pending Vulnerabilities, Solutions, and Work-Arounds: - See SUSE Security Summary Report 6) Authenticity Verification and Additional Information ______________________________________________________________________________ 1) Problem Description and Brief Discussion This update fixes various security issues and some bugs in the SUSE Linux Enterprise 9 kernel. Following security issues were fixed: CVE-2010-2521: A crafted NFS writerequest might have caused a buffer overwrite, potentially causing a kernel crash. CVE-2008-0598: The x86_64 copy_to_user implementation might have leaked kernel memory depending on specific user buffer setups. CVE-2009-4537: drivers/net/r8169.c in the r8169 driver in the Linux kernel did not properly check the size of an Ethernet frame that exceeds the MTU, which allows remote attackers to (1) cause a denial of service (temporary network outage) via a packet with a crafted size, in conjunction with certain packets containing A characters and certain packets containing E characters; or (2) cause a denial of service (system crash) via a packet with a crafted size, in conjunction with certain packets containing '\0' characters, related to the value of the status register and erroneous behavior associated with the RxMaxSize register. NOTE: this vulnerability exists because of an incorrect fix for CVE-2009-1389. CVE-2010-1188: Use-after-free vulnerability in net/ipv4/tcp_input.c in the Linux kernel 2.6 when IPV6_RECVPKTINFO is set on a listening socket, allowed remote attackers to cause a denial of service (kernel panic) via a SYN packet while the socket is in a listening (TCP_LISTEN) state, which is not properly handled causes the skb structure to be freed. CVE-2008-3275: The (1) real_lookup and (2) __lookup_hash functions in fs/namei.c in the vfs implementation in the Linux kernel did not prevent creation of a child dentry for a deleted (aka S_DEAD) directory, which allowed local users to cause a denial of service ("overflow" of the UBIFS orphan area) via a series of attempted file creations within deleted directories. CVE-2007-6733: The nfs_lock function in fs/nfs/file.c in the Linux kernel did not properly remove POSIX locks on files that are setgid without group-execute permission, which allows local users to cause a denial of service (BUG and system crash) by locking a file on an NFS filesystem and thenchanging this files permissions, a related issue to CVE-2010-0727. CVE-2007-6206: The do_coredump function in fs/exec.c in Linux kernel did not change the UID of a core dump file if it exists before a root process creates a core dump in the same location, which might have allowed local users to obtain sensitive information. CVE-2010-1088: fs/namei.c in the Linux kernel did not always follow NFS automount "symlinks," which allowed attackers to have an unknown impact, related to LOOKUP_FOLLOW. CVE-2009-4020: Stack-based buffer overflow in the hfs subsystem in the Linux kernel allowed remote attackers to have an unspecified impact via a crafted Hierarchical File System (HFS) filesystem, related to the hfs_readdir function in fs/hfs/dir.c. CVE-2010-1083: The processcompl_compat function in drivers/usb/core/devio.c in Linux kernel did not clear the transfer buffer before returning to userspace when a USB command fails, which might have made it easier for physically proximate attackers to obtain sensitive information (kernel memory). 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes Please reboot the machine after installing the update. 4) Package Location and Checksums The preferred method for installing security updates is to use the YaST Online Update (YOU) tool. YOU detects which updates are required and automatically performs the necessary steps to verify and install them. Alternatively, download the update packages for your distribution manually and verify their integrity by the methods listed in Section 6 of this announcement. Then install the packages using the command rpm -Fhv to apply the update, replacing with the filename of the downloaded RPM package. Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: SUSE CORE 9 for AMD64 and IntelEM64T SUSE CORE 9 for IBM zSeries 64bit SUSE CORE 9 for IBM S/390 31bit SUSE CORE 9 for IBM POWER SUSE CORE 9 for Itanium Processor Family Novell Linux POS 9 SUSE SLES 9 SUSE CORE 9 for x86 Open Enterprise Server ______________________________________________________________________________ 5) Pending Vulnerabilities, Solutions, and Work-Arounds: - See SUSE Security Summary Report ______________________________________________________________________________ 6) Authenticity Verification and Additional Information - Announcement authenticity verification: SUSE security announcements are published via mailing lists and on Web sites. The authenticity and integrity of a SUSE security announcement is guaranteed by a cryptographic signature in each announcement. All SUSE security announcements are published with a valid signature. To verify the signature of the announcement, save it as text into a file and run the command gpg --verify replacing with the name of the file where you saved the announcement. The output for a valid signature looks like: gpg: Signature made using RSA key ID 3D25D3D9 gpg: Good signature from "SuSE Security Team " where is replaced by the date the document was signed. If the security team's key is not contained in your key ring, you can import it from the first installation CD. To import the key, use the command gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc - Package authenticity verification: SUSE update packages are available on many mirror FTP servers all over the world. While this service is considered valuable and important to the free and open source software community, the authenticity and the integrity of a package needs to be verified to ensure that it has not been tampered with. The internal rpm package signaturesprovide an easy way to verify the authenticity of an RPM package. Use the command rpm -v --checksig to verify the signature of the package, replacing with the filename of the RPM package downloaded. The package is unmodified if it contains a valid signature from
Sep 01, 2010
•Important
SuSE
98
security advisoryRed Hat Enterprise LinuximportantRed Hat 5.2 RHSA-2010:0079 Important Kernel Security Update
Updated kernel packages that fix multiple security issues and several bugs are now available for Red Hat Enterprise Linux 5.2 Extended Update Support. This update has been rated as having important security impact by the Red Hat Security Response Team.. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ==================================================================== Red Hat Security Advisory Synopsis: Important: kernel security and bug fix update Advisory ID: RHSA-2010:0079-01 Product: Red Hat Enterprise Linux Advisory URL: https://access.redhat.com/errata/RHSA-2010:0079.html Issue date: 2010-02-02 CVE Names: CVE-2007-4567 CVE-2007-5966 CVE-2009-0778 CVE-2009-0834 CVE-2009-1385 CVE-2009-1895 CVE-2009-4536 CVE-2009-4537 CVE-2009-4538 ==================================================================== 1. Summary: Updated kernel packages that fix multiple security issues and several bugs are now available for Red Hat Enterprise Linux 5.2 Extended Update Support. This update has been rated as having important security impact by the Red Hat Security Response Team. 2. Relevant releases/architectures: Red Hat Enterprise Linux (v. 5.2.z server) - i386, ia64, noarch, ppc, s390x, x86_64 3. Description: The kernel packages contain the Linux kernel, the core of any Linux operating system. This update fixes the following security issues: * a flaw was found in the IPv6 Extension Header (EH) handling implementation in the Linux kernel. The skb-> dst data structure was not properly validated in the ipv6_hop_jumbo() function. This could possibly lead to a remote denial of service. (CVE-2007-4567, Important) * the possibility of a timeout value overflow was found in the Linux kernel high-resolution timers functionality, hrtimers. This could allow a local, unprivileged user to execute arbitrary code, or cause a denial of service (kernel panic). (CVE-2007-5966, Important) * memory leaks were found on some errorpaths in the icmp_send() function in the Linux kernel. This could, potentially, cause the network connectivity to cease. (CVE-2009-0778, Important) * a deficiency was found in the Linux kernel system call auditing implementation on 64-bit systems. This could allow a local, unprivileged user to circumvent a system call audit configuration, if that configuration filtered based on the "syscall" number or arguments. (CVE-2009-0834, Important) * a flaw was found in the Intel PRO/1000 Linux driver (e1000) in the Linux kernel. Frames with sizes near the MTU of an interface may be split across multiple hardware receive descriptors. Receipt of such a frame could leak through a validation check, leading to a corruption of the length check. A remote attacker could use this flaw to send a specially-crafted packet that would cause a denial of service or code execution. (CVE-2009-1385, Important) * the ADDR_COMPAT_LAYOUT and MMAP_PAGE_ZERO flags were not cleared when a setuid or setgid program was executed. A local, unprivileged user could use this flaw to bypass the mmap_min_addr protection mechanism and perform a NULL pointer dereference attack, or bypass the Address Space Layout Randomization (ASLR) security feature. (CVE-2009-1895, Important) * a flaw was found in each of the following Intel PRO/1000 Linux drivers in the Linux kernel: e1000 and e1000e. A remote attacker using packets larger than the MTU could bypass the existing fragment check, resulting in partial, invalid frames being passed to the network stack. These flaws could also possibly be used to trigger a remote denial of service. (CVE-2009-4536, CVE-2009-4538, Important) * a flaw was found in the Realtek r8169 Ethernet driver in the Linux kernel. Receiving overly-long frames with a certain revision of the network cards supported by this driver could possibly result in a remote denial of service. (CVE-2009-4537, Important) Note: This update also fixes several bugs. Documentation for these bug fixes will be available shortlyfrom https://docs.redhat.com/en/ index.html Users should upgrade to these updated packages, which contain backported patches to correct these issues. The system must be rebooted for this update to take effect. 4. Solution: Before applying this update, make sure that all previously-released errata relevant to your system have been applied. This update is available via Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at 5. Bugs fixed (http://bugzilla.redhat.com/): 453135 - CVE-2007-5966 kernel: non-root can trigger cpu_idle soft lockup 485163 - CVE-2009-0778 kernel: rt_cache leak leads to lack of network connectivity 487990 - CVE-2009-0834 kernel: x86-64: syscall-audit: 32/64 syscall hole 502981 - CVE-2009-1385 kernel: e1000_clean_rx_irq() denial of service 511171 - CVE-2009-1895 kernel: personality: fix PER_CLEAR_ON_SETID 524179 - Frequent path failures during I/O on DM multipath devices [rhel-5.2.z] 546226 - RHEL5.2/3 - setpgid() returns ESRCH in some situations [rhel-5.2.z] 546227 - [5.3] clock_gettime() syscall returns a smaller timespec value than previous. [rhel-5.2.z] 546228 - [5.3] The nanosleep() syscall sleeps one second longer. [rhel-5.2.z] 546229 - [RHEL 5] gen_estimator deadlock fix [rhel-5.2.z] 546230 - softlockups due to infinite loops in posix_locks_deadlock [rhel-5.2.z] 546231 - crm #1896100 port epoll_wait fix from RHSA-2008-0665 to RHEL 5 [rhel-5.2.z] 546232 - NFS problem#3 of IT 106473 - 32-bit jiffy wrap around - NFS inode [rhel-5.2.z] 546233 - [RHEL5.2] nfs_getattr() hangs during heavy write workloads [rhel-5.2.z] 546234 - Deadlock in flush_workqueue() results in hung nfs clients [rhel-5.2.z] 546236 - Kernel panic in auth_rpcgss:__gss_find_upcall [rhel-5.2.z] 547299 - RHEL5.3.z LTP nanosleep02 Test Case Failure on Fujitsu Machine [rhel-5.2.z] 548074 - [5.3]Write operation with O_NONBLOCK flag to TTY terminal is blocked [rhel-5.2.z] 548641 - CVE-2007-4567 kernel: ipv6_hop_jumbo remote system crash 550907 - CVE-2009-4537 kernel: r8169 issuereported at 26c3 551214 - CVE-2009-4538 kernel: e1000e frame fragment issue 552126 - CVE-2009-4536 kernel: e1000 issue reported at 26c3 553133 - RHSA-2008:0508 linux-2.6.9-x86_64-copy_user-zero-tail.patch broken [rhel-5.2.z] 555052 - setitimer(ITIMER_REAL, ...) failing in 64bit enviroment [rhel-5.2.z] 6. Package List: Red Hat Enterprise Linux (v. 5.2.zserver): Source: kernel-2.6.18-92.1.35.el5.src.rpm i386: kernel-2.6.18-92.1.35.el5.i686.rpm kernel-PAE-2.6.18-92.1.35.el5.i686.rpm kernel-PAE-debuginfo-2.6.18-92.1.35.el5.i686.rpm kernel-PAE-devel-2.6.18-92.1.35.el5.i686.rpm kernel-debug-2.6.18-92.1.35.el5.i686.rpm kernel-debug-debuginfo-2.6.18-92.1.35.el5.i686.rpm kernel-debug-devel-2.6.18-92.1.35.el5.i686.rpm kernel-debuginfo-2.6.18-92.1.35.el5.i686.rpm kernel-debuginfo-common-2.6.18-92.1.35.el5.i686.rpm kernel-devel-2.6.18-92.1.35.el5.i686.rpm kernel-headers-2.6.18-92.1.35.el5.i386.rpm kernel-xen-2.6.18-92.1.35.el5.i686.rpm kernel-xen-debuginfo-2.6.18-92.1.35.el5.i686.rpm kernel-xen-devel-2.6.18-92.1.35.el5.i686.rpm ia64: kernel-2.6.18-92.1.35.el5.ia64.rpm kernel-debug-2.6.18-92.1.35.el5.ia64.rpm kernel-debug-debuginfo-2.6.18-92.1.35.el5.ia64.rpm kernel-debug-devel-2.6.18-92.1.35.el5.ia64.rpm kernel-debuginfo-2.6.18-92.1.35.el5.ia64.rpm kernel-debuginfo-common-2.6.18-92.1.35.el5.ia64.rpm kernel-devel-2.6.18-92.1.35.el5.ia64.rpm kernel-headers-2.6.18-92.1.35.el5.ia64.rpm kernel-xen-2.6.18-92.1.35.el5.ia64.rpm kernel-xen-debuginfo-2.6.18-92.1.35.el5.ia64.rpm kernel-xen-devel-2.6.18-92.1.35.el5.ia64.rpm noarch: kernel-doc-2.6.18-92.1.35.el5.noarch.rpm ppc: kernel-2.6.18-92.1.35.el5.ppc64.rpm kernel-debug-2.6.18-92.1.35.el5.ppc64.rpm kernel-debug-debuginfo-2.6.18-92.1.35.el5.ppc64.rpm kernel-debug-devel-2.6.18-92.1.35.el5.ppc64.rpm kernel-debuginfo-2.6.18-92.1.35.el5.ppc64.rpm kernel-debuginfo-common-2.6.18-92.1.35.el5.ppc64.rpm kernel-devel-2.6.18-92.1.35.el5.ppc64.rpm kernel-headers-2.6.18-92.1.35.el5.ppc.rpm kernel-headers-2.6.18-92.1.35.el5.ppc64.rpm kernel-kdump-2.6.18-92.1.35.el5.ppc64.rpm kernel-kdump-debuginfo-2.6.18-92.1.35.el5.ppc64.rpm kernel-kdump-devel-2.6.18-92.1.35.el5.ppc64.rpm s390x: kernel-2.6.18-92.1.35.el5.s390x.rpm kernel-debug-2.6.18-92.1.35.el5.s390x.rpm kernel-debug-debuginfo-2.6.18-92.1.35.el5.s390x.rpm kernel-debug-devel-2.6.18-92.1.35.el5.s390x.rpm kernel-debuginfo-2.6.18-92.1.35.el5.s390x.rpm kernel-debuginfo-common-2.6.18-92.1.35.el5.s390x.rpm kernel-devel-2.6.18-92.1.35.el5.s390x.rpm kernel-headers-2.6.18-92.1.35.el5.s390x.rpm kernel-kdump-2.6.18-92.1.35.el5.s390x.rpm kernel-kdump-debuginfo-2.6.18-92.1.35.el5.s390x.rpm kernel-kdump-devel-2.6.18-92.1.35.el5.s390x.rpm x86_64: kernel-2.6.18-92.1.35.el5.x86_64.rpm kernel-debug-2.6.18-92.1.35.el5.x86_64.rpm kernel-debug-debuginfo-2.6.18-92.1.35.el5.x86_64.rpm kernel-debug-devel-2.6.18-92.1.35.el5.x86_64.rpm kernel-debuginfo-2.6.18-92.1.35.el5.x86_64.rpm kernel-debuginfo-common-2.6.18-92.1.35.el5.x86_64.rpm kernel-devel-2.6.18-92.1.35.el5.x86_64.rpm kernel-headers-2.6.18-92.1.35.el5.x86_64.rpm kernel-xen-2.6.18-92.1.35.el5.x86_64.rpm kernel-xen-debuginfo-2.6.18-92.1.35.el5.x86_64.rpm kernel-xen-devel-2.6.18-92.1.35.el5.x86_64.rpm These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from https://access.redhat.com/security/team/key#package 7. References: https://access.redhat.com/security/cve/CVE-2007-4567 https://access.redhat.com/security/cve/CVE-2007-5966 https://access.redhat.com/security/cve/CVE-2009-0778 https://access.redhat.com/security/cve/CVE-2009-0834 https://access.redhat.com/security/cve/CVE-2009-1385 https://access.redhat.com/security/cve/CVE-2009-1895 https://access.redhat.com/security/cve/CVE-2009-4536 https://access.redhat.com/security/cve/CVE-2009-4537 https://access.redhat.com/security/cve/CVE-2009-4538 https://access.redhat.com/security/updates/classification#important https://docs.redhat.com/en 8. Contact: The Red Hat security contact is . More contact details at https://access.redhat.com/security/team/contact/ Copyright 2010 Red Hat, Inc. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (GNU/Linux) iD8DBQFLaJNIXlSAg2UNWIIRAsQrAKC7nYXA7y9ze6eL7xMo2MCZqDnzYgCfX1Wn V6eoXfbGsp1woczITyf7nQ4=BfMH -----END PGP SIGNATURE----- -- Enterprise-watch-list mailing list
Feb 02, 2010
•Important
Red Hat
100
security advisorysecurity issuekernel updateSUSE Linux Enterprise 9: 2009-015 Moderate: Kernel Remote Denial Of Service
The SUSE Linux Enterprise 9 kernel has been updated to fix lots of bugs The SUSE Linux Enterprise 9 kernel has been updated to fix lots of bugs and several security issues. and several security issues. Following security issues were fixed: CVE-2009-0028: The clone system call in the Linux kernel allows local users to send arbitrary signals to a parent process from an unprivileged child process by [More...]. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: kernel Announcement ID: SUSE-SA:2009:015 Date: Fri, 03 Apr 2009 11:00:00 +0000 Affected Products: SUSE SLES 9 Novell Linux Desktop 9 Open Enterprise Server Novell Linux POS 9 Vulnerability Type: remote denial of service Severity (1-10): 7 SUSE Default Package: yes Cross-References: CVE-2009-0028, CVE-2009-0065, CVE-2009-0322 CVE-2009-0675, CVE-2009-0676 Content of This Advisory: 1) Security Vulnerability Resolved: Linux kernel security update Problem Description 2) Solution or Work-Around 3) Special Instructions and Notes 4) Package Location and Checksums 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. 6) Authenticity Verification and Additional Information ______________________________________________________________________________ 1) Problem Description and Brief Discussion The SUSE Linux Enterprise 9 kernel has been updated to fix lots of bugs and several security issues. Following security issues were fixed: CVE-2009-0028: The clone system call in the Linux kernel allows local users to send arbitrary signals to aparent process from an unprivileged child process by launching an additional child process with the CLONE_PARENT flag, and then letting this new process exit. CVE-2009-0675: The skfp_ioctl function in drivers/net/skfp/skfddi.c in the Linux kernel permits SKFP_CLR_STATS requests only when the CAP_NET_ADMIN capability is absent, instead of when this capability is present, which allows local users to reset the driver statistics, related to an "inverted logic" issue. CVE-2009-0676: The sock_getsockopt function in net/core/sock.c in the Linux kernel does not initialize a certain structure member, which allows local users to obtain potentially sensitive information from kernel memory via an SO_BSDCOMPAT getsockopt request. CVE-2009-0322: drivers/firmware/dell_rbu.c in the Linux kernel allows local users to cause a denial of service (system crash) via a read system call that specifies zero bytes from the (1) image_type or (2) packet_size file in /sys/devices/platform/dell_rbu/. CVE-2009-0065: Buffer overflow in net/sctp/sm_statefuns.c in the Stream Control Transmission Protocol (sctp) implementation in the Linux kernel allows remote attackers to have an unknown impact via an FWD-TSN (aka FORWARD-TSN) chunk with a large stream ID. The update was already released last Friday. 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes Please reboot the machine after installing the update. 4) Package Location and Checksums The preferred method for installing security updates is to use the YaST Online Update (YOU) tool. YOU detects which updates are required and automatically performs the necessary steps to verify and install them. Alternatively, download the update packages for your distribution manually and verify their integrity by the methods listed in Section 6 of this announcement. Then install the packages using the command rpm -Fhv to apply theupdate, replacing with the filename of the downloaded RPM package. Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: Novell Linux Desktop 9 for x86 Open Enterprise Server Novell Linux POS 9 SUSE CORE 9 for x86 SUSE CORE 9 for AMD64 and Intel EM64T SUSE CORE 9 for IBM zSeries 64bit SUSE CORE 9 for IBM S/390 31bit SUSE CORE 9 for IBM POWER SUSE SLES 9 SUSE CORE 9 for Itanium Processor Family Novell Linux Desktop 9 Novell Linux Desktop 9 for x86_64 ______________________________________________________________________________ 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. ______________________________________________________________________________ 6) Authenticity Verification and Additional Information - Announcement authenticity verification: SUSE security announcements are published via mailing lists and on Web sites. The authenticity and integrity of a SUSE security announcement is guaranteed by a cryptographic signature in each announcement. All SUSE security announcements are published with a valid signature. To verify the signature of the announcement, save it as text into a file and run the command gpg --verify replacing with the name of the file where you saved the announcement. The output for a valid signature looks like: gpg: Signature made using RSA key ID 3D25D3D9 gpg: Good signature from "SuSE Security Team " where is replaced by the date the document was signed. If the security team's key is not contained in your key ring, you can import it from the first installation CD. To import the key, use the command gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc - Package authenticity verification: SUSE updatepackages are available on many mirror FTP servers all over the world. While this service is considered valuable and important to the free and open source software community, the authenticity and the integrity of a package needs to be verified to ensure that it has not been tampered with. The internal rpm package signatures provide an easy way to verify the authenticity of an RPM package. Use the command rpm -v --checksig to verify the signature of the package, replacing with the filename of the RPM package downloaded. The package is unmodified if it contains a valid signature from
Apr 03, 2009
•Important
SuSE
100
security advisorysecurity issueupdateSUSE: 2007-021 Moderate: Kernel Remote Denial Of Service Threats
The Linux kernel was updated to fix the security problems listed below. The Linux kernel was updated to fix the security problems listed below. This advisory is for the bugs already announced for SUSE Linux Enterprise 10 and SUSE Linux 10.1 in SUSE-SA:2007:018. The packages associated with this update were already released 1 week ago.. -----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SUSE Security Announcement Package: kernel Announcement ID: SUSE-SA:2007:021 Date: Fri, 16 Mar 2007 13:00:00 +0000 Affected Products: SUSE LINUX 10.0 openSUSE 10.2 Vulnerability Type: remote denial of service Severity (1-10): 7 SUSE Default Package: yes Cross-References: CVE-2006-2936, CVE-2006-5749, CVE-2006-5751 CVE-2006-5753, CVE-2006-6106, CVE-2007-0006 CVE-2007-0772 Content of This Advisory: 1) Security Vulnerability Resolved: kernel security update Problem Description 2) Solution or Work-Around 3) Special Instructions and Notes 4) Package Location and Checksums 5) Pending Vulnerabilities, Solutions, and Work-Arounds: none 6) Authenticity Verification and Additional Information ______________________________________________________________________________ 1) Problem Description and Brief Discussion The Linux kernel was updated to fix the security problems listed below. This advisory is for the bugs already announced for SUSE Linux Enterprise 10 and SUSE Linux 10.1 in SUSE-SA:2007:018. The packages associated with this update were already released 1 week ago. Please note that bootloader handling in openSUSE 10.2 has changed and now creates new entries for updated kernels and make those the default. We also had reports of the update breaking the bootloader configuration, and apologize for the inconveniences caused. We are investigating those problems and hope to release an update to fix the bootloader handling code. If you are manually adapting /boot/grub/menu.lst, please review this file after the update. - CVE-2006-2936: The ftdi_sio driver allowed local users to cause a denial of service (memory consumption) by writing more data to the serial port than the hardware can handle, which causes the data to be queued. This requires this driver to be loaded, which only happens if such a device is plugged in. - CVE-2006-5751: An integer overflow in the networking bridge ioctl starting with Kernel 2.6.7 could be used by local attackers to overflow kernel memory buffers and potentially escalate privileges. - CVE-2006-6106: Multiple buffer overflows in the cmtp_recv_interopmsg function in the Bluetooth driver (net/bluetooth/cmtp/capi.c) in the Linux kernel allowed remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via CAPI messages with a large value for the length of the (1) manu (manufacturer) or (2) serial (serial number) field. - CVE-2006-5749: The isdn_ppp_ccp_reset_alloc_state function in drivers/isdn/isdn_ppp.c in the Linux kernel does not call the init_timer function for the ISDN PPP CCP reset state timer, which has unknown attack vectors and results in a system crash. - CVE-2006-5753: Unspecified vulnerability in the listxattr system call in Linux kernel, when a "bad inode" is present, allows local users to cause a denial of service (data corruption) and possibly gain privileges. - CVE-2007-0006: The key serial number collision avoidance code in the key_alloc_serial function allows local users to cause a denial of service (crash) via vectors that trigger a null dereference. - CVE-2007-0772: A remote denial of service problem onNFSv2 mounts with ACL enabled was fixed. Furthermore, openSUSE 10.2 catches up to the mainline kernel, version 2.6.18.8, and contains a large number of additional fixes for non security bugs. 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes Please reboot the system after installing the updated packages. Review the /boot/grub/menu.lst configuration file if you manually changed it. 4) Package Location and Checksums The preferred method for installing security updates is to use the YaST Online Update (YOU) tool. YOU detects which updates are required and automatically performs the necessary steps to verify and install them. Alternatively, download the update packages for your distribution manually and verify their integrity by the methods listed in Section 6 of this announcement. Then install the packages using the command rpm -Fhv to apply the update, replacing with the filename of the downloaded RPM package. x86 Platform: openSUSE 10.2: e82b0a67a4b0bbb0971bb969c8d9eb60 60c6ce6820d3839ce9fbe2eb4bab356c da0bf89980c93e0a475e37fa200e28b0 4bf99d7816ba585f0ed5593dc6fbb740 13bc3b2be8b6fd08ae1589f9cfd67be7 08da4cbf6da45be1c0459580cb44749c 112d3fcfbea319940262c0a306da85be 3096d2eeb901ee592a06d68ca91982a9 9429c6f7042ebd28831298058467044a d2cd5d41af38cf5489b9b7636546ce39 1c01b355d52b01f8cacbdfb06af0c171 d402122d25eab3352c194a96a249cc20 8798fe7a1d4ce2b2029bf4ee957efe08 dd3d8c1869f08c6c9d7821fd122d7b99 d1b16cbbc1445c7564bcdc8f009760a6 ba2fbb5381abcfac608f6dfd9ccca71c bda4e19bab973eace8b245b82a976610 3998dbfbad2955c876d3c6918e30775b 20710daf7c1e1c7560387605e679e9ef 02dcd27ebad0f8b4eeaba2567ef79352 caea9f949b562b7fbe6cc1e5f7da4a4c SUSE LINUX 10.0: 70a42a7f7742d66894bee17b3f388a5d 16b76176c41ecc466f9fb46cdd230489 062a8b04cb89e3989d305bef87dc0757 faf638689b69c1e80569bc46dbfe088b 6049934f03e60aca2bc5d54012c0407d 6c1ac1600ee0f27e7464e0407405f9aa 752faf01a1b41613c91f785e72895a55 e5fe6448fddbc8fcefd8a90b36888db9 e38e9ba4c63044e5bfbb285911c898a5 0944ef9eb3fe1634bf21121bf1f51fdc 9e6bd3a6f743926b9270872fefb9b915 9d49e4767426613e38573037776f26b0 8e5f25c2e2b85129f91c22c6868f0003 a38b42695a1f0700ac1ed8a71c79520c Power PC Platform: openSUSE 10.2: 56d9d481c3c62f9627f8fdb5b3df782d 109afa91f06beb989faa4ce3b5181ffa 1ce2d7597556be60d09b3cea3639af8a 84bd64a7f8d3de26f13536635983be23 56e7429616a92898cbf83ee796ae45f7 f79c0143fbf4ffd0cf14fa616968da58 97ab79266d28d0b05c7fe715e054bce1 SUSE LINUX 10.0: 419939cc75cdf648342e2de9bda2c0e8 5147690fdc8e20d2456d9a2ad9566c15 29982397729967c8237643d59f0a300b 6cf3159d8cef06756309a58f3a007e29 d16442f15524102ab709419e8a56f6a7 x86-64 Platform: openSUSE 10.2: c3841ced488b344daa86646138e1a050 a35ed0949cc2fe69362069398621788d c884bd668d92648dddc440c931b44399 0aed77eee5442d9315f3d53c2da9f6f3 a37c3f4a169d9061af48d1430c04d05f 0c2f6be06580c9ca0426243c73e3144e 74d9189894b2ca61f495dc90023b279a b0880efb1ff8ab29ea0ed752f692985d 8df8f3c772f884481a122abbe264c45d SUSE LINUX 10.0: 9bb317c036977483961d7d4ab2c3a123 a57e4271abb5b607dcf24ccb7c75d3ea 7c0fd656bf08fa0a1dd9bce20ced8b2a a5f66edd202201ffb96eadeb03a7213c f195f6ebb24ef1b6ebf6859efe4e9658 9b23bb08beccedecc5ce35e1b099ca2f a34f4798ccf607f3e6e8c1db4ce6ab1c 3aa25da4d80b5687b0dd112ccbb980f2 Sources: openSUSE 10.2: a6bb16929d315cf146675e75b3e14e97 d18038925c29a061a23fdbd3c410d362 e579ee0834be9cc99f0f181f4eefc722 099041a3de7a607b414c5690dc870117 7f7c7fd1543e01c24c1b9e7f71fb73a1 10d98ce9df7766e3a2268f103bea42d9 058b58f8be113977a91e94ab94bf0182 210b549a27e3eca6d7174ad1c3e4c858 SUSE LINUX 10.0: e7669014790db2d2b9022d08307d7fba a56233e08afeb0c3e7a7d47c4614fcc2 6b84ee8f314841da371d89efe4406e47 28a33e95d59a0fbfa8d7ec10d8bb7d43 f6e51f0333e0b8a571f6e7e070ac577d fb5e7d691e697ae608e9964966060cdc 0bb6955fcaf7079ec5dc84d0242d518a e4f1f529be352d96e39efd832bb1bd2b 44acc7bf9de3e6404876c72a264448d2 80a8dd4f5c4535c6f6cfc40b4d17591a 1b20f3e5ee1bf0b081a50f26f811b47e ______________________________________________________________________________ 5) Pending Vulnerabilities, Solutions, and Work-Arounds: none ______________________________________________________________________________ 6) Authenticity Verification and Additional Information - Announcement authenticity verification: SUSE security announcements are published via mailing lists and on Web sites. The authenticity and integrity of a SUSE security announcement is guaranteed by a cryptographic signature in each announcement. All SUSE security announcements are published with a valid signature. To verify the signature of the announcement, save it as text into a file and run the command gpg --verify replacing with the name of the file where you saved the announcement. The output for a valid signature looks like: gpg: Signature made using RSA key ID 3D25D3D9 gpg: Good signature from "SuSE Security Team " where isreplaced by the date the document was signed. If the security team's key is not contained in your key ring, you can import it from the first installation CD. To import the key, use the command gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc - Package authenticity verification: SUSE update packages are available on many mirror FTP servers all over the world. While this service is considered valuable and important to the free and open source software community, the authenticity and the integrity of a package needs to be verified to ensure that it has not been tampered with. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or RPM package: 1) Using the internal gpg signatures of the rpm package 2) MD5 checksums as provided in this announcement 1) The internal rpm package signatures provide an easy way to verify the authenticity of an RPM package. Use the command rpm -v --checksig to verify the signature of the package, replacing with the filename of the RPM package downloaded. The package is unmodified if it contains a valid signature from
Mar 16, 2007
•Important
SuSE
100
security advisorymoderateetherealSUSE: 2023-045 Moderate: Libcurl Remote Exploitation Vulnerability
Various problems have been fixed in the network analyzer Ethereal (now called Various problems have been fixed in the network analyzer Ethereal (now called Wireshark), most of them leading to crashes of the ethereal program. Wireshark), most of them leading to crashes of the ethereal program. CVE-2006-5740: An unspecified vulnerability in the LDAP dissector could be used to crash Ethereal. CVE-2 [More...]. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: ethereal Announcement ID: SUSE-SA:2006:065 Date: Tue, 14 Nov 2006 11:00:00 +0000 Affected Products: Novell Linux POS 9 Open Enterprise Server SUSE LINUX 10.1 SUSE LINUX 10.0 SUSE LINUX 9.3 SuSE Linux Enterprise Server 8 SuSE Linux Openexchange Server 4 SUSE LINUX Retail Solution 8 SuSE Linux School Server SuSE Linux Standard Server 8 SUSE SLED 10 SUSE SLES 10 SUSE SLES 9 UnitedLinux 1.0 Vulnerability Type: remote denial of service Severity (1-10): 5 SUSE Default Package: no Cross-References: CVE-2006-4574, CVE-2006-4805, CVE-2006-5468 CVE-2006-5469, CVE-2006-5740 Content of This Advisory: 1) Security Vulnerability Resolved: several security problems in wireshark/ethereal Problem Description 2) Solution or Work-Around 3) Special Instructions and Notes 4) Package Location and Checksums 5)Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. 6) Authenticity Verification and Additional Information ______________________________________________________________________________ 1) Problem Description and Brief Discussion Various problems have been fixed in the network analyzer Ethereal (now called Wireshark), most of them leading to crashes of the ethereal program. CVE-2006-5740: An unspecified vulnerability in the LDAP dissector could be used to crash Ethereal. CVE-2006-4574: A single \0 byte heap overflow was fixed in the MIME multipart dissector. Potential of exploitability is unknown, but considered low. CVE-2006-4805: A denial of service problem in the XOT dissector can cause it to take up huge amount of memory and crash ethereal. CVE-2006-5469: The WBXML dissector could be used to crash ethereal. CVE-2006-5468: A NULL pointer dereference in the HTTP dissector could crash ethereal. 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes None. 4) Package Location and Checksums The preferred method for installing security updates is to use the YaST Online Update (YOU) tool. YOU detects which updates are required and automatically performs the necessary steps to verify and install them. Alternatively, download the update packages for your distribution manually and verify their integrity by the methods listed in Section 6 of this announcement. Then install the packages using the command rpm -Fhv to apply the update, replacing with the filename of the downloaded RPM package. x86 Platform: SUSE LINUX 10.1: 6aecc0deb29a6339f1fa941c65844c6d 4c207d76c0f0ada418b790dadcff33f5 SUSE LINUX 10.0: 2f904b719bfbed232744856a4f9eca91 f6957aa0c03893d7fd47873999aaf5c1 SUSE LINUX 9.3: 74cf82fc2bc0a400ca64c66d45064847 PowerPC Platform: SUSE LINUX 10.1: 1c832fcde7f65332e9d0b47274229f69 7f303f1eeccd68a1eee8057f56807a3f SUSE LINUX 10.0: 542ae786e2cb511767c7a4e6449b80cf 178014fc85ec3a0ca43ed9b8ed1cdd26 x86-64 Platform: SUSE LINUX 10.1: 30ca5d51e0f3e889b31a59bad4611dfc 2990cb62f731d700675a75203bbd5aa7 SUSE LINUX 10.0: 542b66bcc88e07faec6c33abda8f5d7c 7a936eff6d66a5574e564c4255e3fa46 SUSE LINUX 9.3: bd6cc27b6b9e05441bacdba249357f5d Sources: SUSE LINUX 10.1: b04b4bb194dfbf4ea92b822149bd3664 SUSE LINUX 10.0: ff3b7fd57d84597700a75f95fbfcc3e7 SUSE LINUX 9.3: b53b87038538e026052356b8a89a0f82 Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: UnitedLinux 1.0 http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html SuSE Linux Openexchange Server 4 http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html Open Enterprise Server http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html Novell Linux POS 9 http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html SuSE Linux Enterprise Server 8 http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html SuSE Linux Standard Server 8 http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html SuSE Linux School Server http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html SUSE LINUX Retail Solution 8 http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html SUSE SLES 10 http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html SUSE SLED 10 http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html SUSE SLES 9 http://support.novell.com/techcenter/psdb/c4745f0c0b9184f32b2201f189dc66f6.html ______________________________________________________________________________ 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. ______________________________________________________________________________ 6) Authenticity Verification and Additional Information - Announcement authenticity verification: SUSE security announcements are published via mailing lists and on Web sites. The authenticity and integrity of a SUSE security announcement is guaranteed by a cryptographic signature in each announcement. All SUSE security announcements are published with a valid signature. To verify the signature of the announcement, save it as text into a file and run the command gpg --verify replacing with the name of the file where you saved the announcement. The output for a valid signature looks like: gpg: Signature made using RSA key ID 3D25D3D9 gpg: Good signature from "SuSE Security Team " where is replaced by the date the document was signed. If the security team's key is not contained in your key ring, you can import it from the first installation CD. To import the key, use the command gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc - Package authenticity verification: SUSE update packages are available on many mirror FTP servers all over the world. While this service is considered valuable and important to the free and open source software community, the authenticity and the integrity of a package needs to be verified to ensure that it has not been tampered with. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or RPM package: 1) Using the internal gpg signatures of the rpm package 2) MD5 checksums as provided in this announcement 1) The internal rpm package signatures providean easy way to verify the authenticity of an RPM package. Use the command rpm -v --checksig to verify the signature of the package, replacing with the filename of the RPM package downloaded. The package is unmodified if it contains a valid signature from
Nov 14, 2006
SuSE
100
security advisorysecurity updatecriticalSUSE Linux 10.0: 2006-006 Critical Kernel Remote Denial of Service
The Linux kernel on SUSE Linux 10.0 has been updated to The Linux kernel on SUSE Linux 10.0 has been updated to fix following security problems: fix following security problems: - CVE-2006-0454: An extra dst release when ip_options_echo failedwas fixed. This problem could be triggered by remote attackers and can. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: kernel Announcement ID: SUSE-SA:2006:006 Date: Thu, 09 Feb 2006 16:00:00 +0000 Affected Products: SUSE LINUX 10.0 Vulnerability Type: remote denial of service Severity (1-10): 9 SUSE Default Package: yes Cross-References: CVE-2005-3356, CVE-2005-3358, CVE-2005-3623 CVE-2005-3808, CVE-2005-4605, CVE-2005-4635 CVE-2006-0454 Content of This Advisory: 1) Security Vulnerability Resolved: various kernel security problems Problem Description 2) Solution or Work-Around 3) Special Instructions and Notes 4) Package Location and Checksums 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. 6) Authenticity Verification and Additional Information ______________________________________________________________________________ 1) Problem Description and Brief Discussion The Linux kernel on SUSE Linux 10.0 has been updated to fix following security problems: - CVE-2006-0454: An extra dst release when ip_options_echo failed was fixed. This problem could be triggered by remote attackers and can potentially crash the machine. This is possible even with SuSEfirewall2 enabled. This affects only SUSE Linux 10.0, all other SUSE distributions are not affected. - CVE-2005-3356:A double decrement in mq_open system call could lead to local users crashing the machine. - CVE-2005-3358: A 0 argument passed to the set_mempolicy() system call could lead to a local user crashing the machine. - CVE-2005-4605: Kernel memory could be leaked to user space through a problem with seek() in /proc files . - CVE-2005-3623: Remote users could set ACLs even on read-only exported NFS Filesystems and so circumvent access control. - CVE-2005-3808: A 32 bit integer overflow on 64bit mmap calls could be used by local users to hang the machine. - CVE-2005-4635: Add sanity checks for headers and payload of netlink messages, which could be used by local attackers to crash the machine. Also various non-security bugs were fixed: - Fix up patch for cpufreq drivers that do not initialize current freq. - Handle BIOS cpufreq changes gracefully. - Updates to inotify handling. - Various XEN Updates. - Catches processor declarations with same ACPI id (P4HT) - PowerPC: g5 thermal overtemp bug on fluid cooled systems. - Fixed buffered ACPI events on a lot ASUS and some other machines. - Fix fs/exec.c:788 (de_thread()) BUG_ON (OSDL 5170). 2) Solution or Work-Around There is no known workaround, please install the updated packages. 3) Special Instructions and Notes SPECIAL INSTALLATION INSTRUCTIONS ================================ The following paragraphs guide you through the installation process in a step-by-step fashion. The character sequence "****" marks the beginning of a new paragraph. In some cases, the steps outlined in a particular paragraph may or may not be applicable to your situation. Therefore, make sure that you read through all of the steps below before attempting any of these procedures. All of the commands that need to be executed must be run as the superuser 'root'. Each step relies on the steps before it to complete successfully. Newer SUSE Linuxversions do all this automatically when running the YaST Online Update. **** Step 1: Determine the needed kernel type. Use the following command to determine which kind of kernel is installed on your system: rpm -qf --qf '%{name}\n' /boot/vmlinuz **** Step 2: Download the packages for your system. Download the kernel RPM package for your distribution with the name indicated by Step 1. Starting from SUSE LINUX 9.2, kernel modules that are not free were moved to a separate package with the suffix '-nongpl' in its name. Download that package as well if you rely on hardware that requires non-free drivers, such as some ISDN adapters. The list of all kernel RPM packages is appended below. The kernel-source package does not contain a binary kernel in bootable form. Instead, it contains the sources that correspond with the binary kernel RPM packages. This package is required to build third party add-on modules. **** Step 3: Verify authenticity of the packages. Verify the authenticity of the kernel RPM package using the methods as listed in Section 6 of this SUSE Security Announcement. **** Step 4: Installing your kernel rpm package. Install the rpm package that you have downloaded in Step 2 with the command rpm -Uhv replacing with the filename of the RPM package downloaded. Warning: After performing this step, your system may not boot unless the following steps have been followed completely. **** Step 5: Configuring and creating the initrd. The initrd is a RAM disk that is loaded into the memory of your system together with the kernel boot image by the boot loader. The kernel uses the content of this RAM disk to execute commands that must be run before the kernel can mount its root file system. The initrd is typically used to load hard disk controller drivers and file system modules. The variable INITRD_MODULES in /etc/sysconfig/kernel determines which kernel modules are loaded in the initrd. After a new kernel rpm has been installed, the initrd must be recreated to include the updated kernel modules. Usually this happens automatically when installing the kernel rpm. If creating the initrd fails for some reason, manually run the command /sbin/mkinitrd **** Step 6: Update the boot loader, if necessary. Depending on your software configuration, you either have the LILO or GRUB boot loader installed and initialized on your system. Use the command grep LOADER_TYPE /etc/sysconfig/bootloader to find out which boot loader is configured. The GRUB boot loader does not require any further action after a new kernel has been installed. You may proceed to the next step if you are using GRUB. If you use the LILO boot loader, lilo must be run to reinitialize the boot sector of the hard disk. Usually this happens automatically when installing the kernel RPM. In case this step fails, run the command /sbin/lilo Warning: An improperly installed boot loader will render your system unbootable. **** Step 7: Reboot. If all of the steps above have been successfully completed on your system, the new kernel including the kernel modules and the initrd are ready to boot. The system needs to be rebooted for the changes to be active. Make sure that all steps have been completed then reboot using the command /sbin/shutdown -r now Your system will now shut down and restart with the new kernel. 4) Package Location and Checksums The preferred method for installing security updates is to use the YaST Online Update (YOU) tool. YOU detects which updates are required and automatically performs the necessary steps to verify and install them. Alternatively, download the update packages for your distribution manually and verify their integrity bythe methods listed in Section 6 of this announcement. Then install the packages using the command rpm -Fhv to apply the update, replacing with the filename of the downloaded RPM package. x86 Platform: SUSE LINUX 10.0: 617123d586215e94e373797650689b7f 0cbb96d083eb5c5cb6f14896b156d3d6 9da719c36eb4119165d5cd70bfb98703 e84cf4f754e2dbad45d32f22764ac363 96556ee27a4a34ad2757fe0605f56e0a 6bcc5556183a30d5be7164229f1a9b2a 78883d88c7cca8f55676c6ad8fae8f74 566deccc17d66d38037829b04cd90bf6 98dd96111ed5932e29f17bdea8785ad4 37d53ae4b23984e6c2c1eccf2cab1418 9486e2bbba0809d01469eb8ce2862e45 916db787417eb6714f4ef29e2b4fc215 c9f178ee29025e37fad02fc97f54a960 b7bd6a96c6f4e484c71121d928ccd88c a45eca7e51d5013a33c911ea1a4cfee2 da838d086ab74ae26217fdefd48536ae 803b0ce83f4a3a08988b3af39f187158 9224d203e3466d1bf9a44ccfa0811471 a9b0794189169f88275922da3e3e8566 3c39e8fadf994ba48c77f429d6d57b89 08559ccb01107e018ac9b1bdf8b6be65 Power PC Platform: SUSE LINUX 10.0: 9809772427eb306647e818d806a77e89 e180170929a1ea8d3f98331bcfb30c9b 87a70ccab5ba54792dee4aa10c793842 b87c03b2d486fd03c3fac0b3d2a6a226 7dade40bb01bd88a8b0fe59d1305f5c8 x86-64 Platform: SUSE LINUX 10.0: 1b257b185e8eedfc3d8fbded87ad78d7 602f86133787c0ecc8eec89b23d54315 1a60423b90616a8cbe9f709f3af24788 95a1d602ec636d83429e326c5d72a6ac 72998ee6616db4d71eb5f6830b02775d 8dbeccfea33a188e645c49d18b489ec8 f8b7244ffdfce6cd10a63793bfff91c1 3a1b868760ccfcd9e58a99d0cc2e6e10 bf63af95f1460384576fe544497a69d9 b40992546fe02ba8c1b575ea0d219459 89ebeb3a359c3bea923579d557ddd799 596a4325239ea8b18dd13a2f32a23fd9 a0dec51273e8b67313cb7001efa4e555 88ec4608838d3c0175412d4f9a3a722b c4d1a2fb18cc12cc670eaecbcc52e51e Sources: SUSE LINUX 10.0: 318b6e58e9618c58b45b442402f02d8d a8106394b8179741f4abe6c5033b825b 15357679ff39d7d172915286cf366a02 4819d48418dd04d54a6a2cc95ae743dd 07716c45346938286197c12459139f1d 1f0626d1a7a4f9512a68787369110323 0d54d3a5531ca860327a42d026d6a5ed de47591367758860be95265cf81a514b 807f7d1ffde7604cf90198237b3db382 859c7778b1138f4a6a650ca855d81d09 131b8f17f1aa4ea060bcc1d3a6148756 75b98cae0e6d1c682e70309bb975060b ______________________________________________________________________________ 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. ______________________________________________________________________________ 6) Authenticity Verification and Additional Information - Announcement authenticity verification: SUSE security announcements are published via mailing lists and on Web sites. The authenticity and integrity of a SUSE security announcement is guaranteed by a cryptographic signature in each announcement. All SUSE security announcements are published with a valid signature. To verify the signature of the announcement, save it as text into a file and run the command gpg --verify replacing with the name of the file where you saved the announcement. The output for a valid signature looks like: gpg: Signature made using RSA key ID 3D25D3D9 gpg: Good signature from "SuSE Security Team " where is replaced by the date the document was signed. If the security team's key is not contained in your key ring, you can import it from the first installation CD. To import the key, use the command gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc -Package authenticity verification: SUSE update packages are available on many mirror FTP servers all over the world. While this service is considered valuable and important to the free and open source software community, the authenticity and the integrity of a package needs to be verified to ensure that it has not been tampered with. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or RPM package: 1) Using the internal gpg signatures of the rpm package 2) MD5 checksums as provided in this announcement 1) The internal rpm package signatures provide an easy way to verify the authenticity of an RPM package. Use the command rpm -v --checksig to verify the signature of the package, replacing with the filename of the RPM package downloaded. The package is unmodified if it contains a valid signature from
Feb 09, 2006
•Critical
SuSE
Get the latest News and Insights
Get the latest Linux and open source security news straight to your inbox.
Community Poll
Should Linux servers automatically install security updates?
Search Topics
Powered By
Linux Security - Your source for Top Linux News, Advisories, HOWTOs and Feature Releases
QUICK LINKS
subscribe to newsletters!
Like staying secure? So do we.
Sign up for updates, tips, and alerts!