Lucene search

K
redhatRedHatRHSA-2008:0885
HistorySep 24, 2008 - 12:00 a.m.

(RHSA-2008:0885) Important: kernel security and bug fix update

2008-09-2400:00:00
access.redhat.com
35

7.8 High

CVSS3

Attack Vector

LOCAL

Attack Complexity

LOW

Privileges Required

LOW

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

HIGH

Integrity Impact

HIGH

Availability Impact

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

7.2 High

CVSS2

Access Vector

LOCAL

Access Complexity

LOW

Authentication

NONE

Confidentiality Impact

COMPLETE

Integrity Impact

COMPLETE

Availability Impact

COMPLETE

AV:L/AC:L/Au:N/C:C/I:C/A:C

0.0004 Low

EPSS

Percentile

8.6%

The kernel packages contain the Linux kernel, the core of any Linux
operating system.

Security fixes:

  • a missing capability check was found in the Linux kernel do_change_type
    routine. This could allow a local unprivileged user to gain privileged
    access or cause a denial of service. (CVE-2008-2931, Important)

  • a flaw was found in the Linux kernel Direct-IO implementation. This could
    allow a local unprivileged user to cause a denial of service.
    (CVE-2007-6716, Important)

  • Tobias Klein reported a missing check in the Linux kernel Open Sound
    System (OSS) implementation. This deficiency could lead to a possible
    information leak. (CVE-2008-3272, Moderate)

  • a deficiency was found in the Linux kernel virtual filesystem (VFS)
    implementation. This could allow a local unprivileged user to attempt file
    creation within deleted directories, possibly causing a denial of service.
    (CVE-2008-3275, Moderate)

  • a flaw was found in the Linux kernel tmpfs implementation. This could
    allow a local unprivileged user to read sensitive information from the
    kernel. (CVE-2007-6417, Moderate)

Bug fixes:

  • when copying a small IPoIB packet from the original skb it was received
    in to a new, smaller skb, all fields in the new skb were not initialized.
    This may have caused a kernel oops.

  • previously, data may have been written beyond the end of an array,
    causing memory corruption on certain systems, resulting in hypervisor
    crashes during context switching.

  • a kernel crash may have occurred on heavily-used Samba servers after 24
    to 48 hours of use.

  • under heavy memory pressure, pages may have been swapped out from under
    the SGI Altix XPMEM driver, causing silent data corruption in the kernel.

  • the ixgbe driver is untested, but support was advertised for the Intel
    82598 network card. If this card was present when the ixgbe driver was
    loaded, a NULL pointer dereference and a panic occurred.

  • on certain systems, if multiple InfiniBand queue pairs simultaneously
    fell into an error state, an overrun may have occurred, stopping traffic.

  • with bridging, when forward delay was set to zero, setting an interface
    to the forwarding state was delayed by one or possibly two timers,
    depending on whether STP was enabled. This may have caused long delays in
    moving an interface to the forwarding state. This issue caused packet loss
    when migrating virtual machines, preventing them from being migrated
    without interrupting applications.

  • on certain multinode systems, IPMI device nodes were created in reverse
    order of where they physically resided.

  • process hangs may have occurred while accessing application data files
    via asynchronous direct I/O system calls.

  • on systems with heavy lock traffic, a possible deadlock may have caused
    anything requiring locks over NFS to stop, or be very slow. Errors such as
    “lockd: server [IP] not responding, timed out” were logged on client
    systems.

  • unexpected removals of USB devices may have caused a NULL pointer
    dereference in kobject_get_path.

  • on Itanium-based systems, repeatedly creating and destroying Windows
    guests may have caused Dom0 to crash, due to the “XENMEM_add_to_physmap”
    hypercall, used by para-virtualized drivers on HVM, being SMP-unsafe.

  • when using an MD software RAID, crashes may have occurred when devices
    were removed or changed while being iterated through. Correct locking is
    now used.

  • break requests had no effect when using “Serial Over Lan” with the Intel
    82571 network card. This issue may have caused log in problems.

  • on Itanium-based systems, module_free() referred the first parameter
    before checking it was valid. This may have caused a kernel panic when
    exiting SystemTap.

Red Hat Enterprise Linux 5 users are advised to upgrade to these updated
packages, which contain backported patches to resolve these issues.

7.8 High

CVSS3

Attack Vector

LOCAL

Attack Complexity

LOW

Privileges Required

LOW

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

HIGH

Integrity Impact

HIGH

Availability Impact

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

7.2 High

CVSS2

Access Vector

LOCAL

Access Complexity

LOW

Authentication

NONE

Confidentiality Impact

COMPLETE

Integrity Impact

COMPLETE

Availability Impact

COMPLETE

AV:L/AC:L/Au:N/C:C/I:C/A:C

0.0004 Low

EPSS

Percentile

8.6%