RHSA-2015:0803: Important: kernel security and bug fix update

Published Apr 14, 2015
·
Updated

The kernel packages contain the Linux kernel, the core of any Linuxoperating system. It was found that the Linux kernel's Infiniband subsystem did not properly sanitize input parameters while registering memory regions fromuser space via the (u)verbs API. A local user with access to a/dev/infiniband/uverbsX device could use this flaw to crash the system or,potentially, escalate their privileges on the system. (CVE-2014-8159,Important) An integer overflow flaw was found in the way the Linux kernel's Frame Buffer device implementation mapped kernel memory to user space via themmap syscall. A local user able to access a frame buffer device file(/dev/fb) could possibly use this flaw to escalate their privileges on thesystem. (CVE-2013-2596, Important) It was found that the parserockridgeinodeinternal() function of the Linux kernel's ISOFS implementation did not correctly check relocateddirectories when processing Rock Ridge child link (CL) tags. An attackerwith physical access to the system could use a specially crafted ISO imageto crash the system or, potentially, escalate their privileges on thesystem. (CVE-2014-5471, CVE-2014-5472, Low)Red Hat would like to thank Mellanox for reporting the CVE-2014-8159 issue.This update also fixes the following bugs: The kernel could sometimes panic due to a possible division by zero in the kernel scheduler. This bug has been fixed by defining a new div64ul()division function and correcting the affected calculation in theprocschedshowtask() function. (BZ#1199898) When repeating a Coordinated Universal Time (UTC) value during a leap second (when the UTC time should be 23:59:60), the International AtomicTime (TAI) timescale previously stopped as the kernel NTP code incrementedthe TAI offset one second too late. A patch has been provided, which fixesthe bug by incrementing the offset during the leap second itself. Now, thecorrect TAI is set during the leap second. (BZ#1201672)All kernel users are advised to upgrade to these updated packages, whichcontain backported patches to correct these issues. The system must berebooted for this update to take effect.

Affected Software

14 affected componentsFixes available
redhat/kernel<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6
redhat/kernel<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6
redhat/kernel-debug<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6
redhat/kernel-debug-debuginfo<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6
redhat/kernel-debug-devel<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6
redhat/kernel-debuginfo<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6
redhat/kernel-devel<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6
redhat/kernel-doc<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6
redhat/kernel-firmware<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6
redhat/kernel-headers<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6
redhat/perf<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6
redhat/perf-debuginfo<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6
redhat/python-perf<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6
redhat/python-perf-debuginfo<2.6.32-358.59.1.el6
2.6.32-358.59.1.el6

Remediation

Event History

Apr 14, 2015
Advisory Published
12:00 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of RHSA-2015:0803?

The severity of RHSA-2015:0803 is classified as critical due to a vulnerability in the Linux kernel's Infiniband subsystem.

2

How do I fix RHSA-2015:0803?

To fix RHSA-2015:0803, users should update to the kernel package version 2.6.32-358.59.1.el6 or later.

3

Which systems are affected by RHSA-2015:0803?

RHSA-2015:0803 affects systems running vulnerable versions of the Red Hat Enterprise Linux kernel.

4

What is the nature of the vulnerability in RHSA-2015:0803?

The vulnerability in RHSA-2015:0803 relates to improper input sanitization in the Linux kernel's Infiniband subsystem.

5

Can I still use my system if it's affected by RHSA-2015:0803?

It is not recommended to continue using an affected system without applying the necessary patches due to the critical nature of the vulnerability.

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