RHSA-2009:1550: Important: kernel security and bug fix update

Published Nov 3, 2009
·
Updated

The kernel packages contain the Linux kernel, the core of any Linuxoperating system.Security fixes: when fput() was called to close a socket, the scmdestroy() function in the Linux kernel could make indirect recursive calls to itself. This could,potentially, lead to a denial of service issue. (CVE-2008-5029, Important) the sendmsg() function in the Linux kernel did not block during UNIX socket garbage collection. This could, potentially, lead to a local denialof service. (CVE-2008-5300, Important) the exitnotify() function in the Linux kernel did not properly reset the exit signal if a process executed a set user ID (setuid) application beforeexiting. This could allow a local, unprivileged user to elevate theirprivileges. (CVE-2009-1337, Important) a flaw was found in the Intel PRO/1000 network driver in the Linux kernel. Frames with sizes near the MTU of an interface may be split acrossmultiple hardware receive descriptors. Receipt of such a frame could leakthrough a validation check, leading to a corruption of the length check. Aremote attacker could use this flaw to send a specially-crafted packet thatwould cause a denial of service or code execution. (CVE-2009-1385,Important) the ADDRCOMPATLAYOUT and MMAPPAGEZERO flags were not cleared when a setuid or setgid program was executed. A local, unprivileged user could usethis flaw to bypass the mmapminaddr protection mechanism and perform aNULL pointer dereference attack, or bypass the Address Space LayoutRandomization (ASLR) security feature. (CVE-2009-1895, Important) it was discovered that, when executing a new process, the clearchildtid pointer in the Linux kernel is not cleared. If this pointer points to awritable portion of the memory of the new program, the kernel could corruptfour bytes of memory, possibly leading to a local denial of service orprivilege escalation. (CVE-2009-2848, Important) missing initialization flaws were found in getname() implementations in the IrDA sockets, AppleTalk DDP protocol, NET/ROM protocol, and ROSEprotocol implementations in the Linux kernel. Certain data structures inthese getname() implementations were not initialized properly before beingcopied to user-space. These flaws could lead to an information leak.(CVE-2009-3002, Important) a NULL pointer dereference flaw was found in each of the following functions in the Linux kernel: pipereadopen(), pipewriteopen(), andpiperdwropen(). When the mutex lock is not held, the ipipe pointer couldbe released by other processes before it is used to update the pipe'sreader and writer counters. This could lead to a local denial of service orprivilege escalation. (CVE-2009-3547, Important)Bug fixes: this update adds the mmapminaddr tunable and restriction checks to help prevent unprivileged users from creating new memory mappings below theminimum address. This can help prevent the exploitation of NULL pointerdereference bugs. Note that mmapminaddr is set to zero (disabled) bydefault for backwards compatibility. (BZ#512642) a bridge reference count problem in IPv6 has been fixed. (BZ#457010) enforce null-termination of user-supplied arguments to setsockopt(). (BZ#505514) the gcc flag "-fno-delete-null-pointer-checks" was added to the kernel build options. This prevents gcc from optimizing out NULL pointer checksafter the first use of a pointer. NULL pointer bugs are often exploited byattackers. Keeping these checks is a safety measure. (BZ#511185) a check has been added to the IPv4 code to make sure that rt is not NULL, to help prevent future bugs in functions that call ipappenddata() frombeing exploitable. (BZ#520300)Users should upgrade to these updated packages, which contain backportedpatches to correct these issues. The system must be rebooted for thisupdate to take effect.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Event History

Nov 3, 2009
Advisory Published
12:00 AM
Data Sourced
12:00 AM
RemedyDescriptionAffected Software

Frequently Asked Questions

1

What is the severity of RHSA-2009:1550?

The severity of RHSA-2009:1550 is classified as moderate.

2

How do I fix RHSA-2009:1550?

To fix RHSA-2009:1550, you should update your kernel package to the latest version provided in the advisory.

3

What vulnerability does RHSA-2009:1550 address?

RHSA-2009:1550 addresses a vulnerability in the Linux kernel related to potential indirect recursive calls in the __scm_destroy() function.

4

Which versions of the Linux kernel are affected by RHSA-2009:1550?

RHSA-2009:1550 affects various versions of the Linux kernel prior to the patched versions released in the advisory.

5

Is RHSA-2009:1550 related to Denial of Service (DoS)?

Yes, the vulnerability described in RHSA-2009:1550 could potentially lead to a Denial of Service condition.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203