RHSA-2018:0152: Important: kernel-rt security and bug fix update
The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.Security Fix(es): A flaw was found in the Linux kernel's key management system where it was possible for an attacker to escalate privileges or crash the machine. If a user key gets negatively instantiated, an error code is cached in the payload area. A negatively instantiated key may be then be positively instantiated by updating it with valid data. However, the ->update key type method must be aware that the error code may be there. (CVE-2015-8539, Important) It was found that fanoutadd() in 'net/packet/afpacket.c' in the Linux kernel, before version 4.13.6, allows local users to gain privileges via crafted system calls that trigger mishandling of packetfanout data structures, because of a race condition (involving fanoutadd and packetdobind) that leads to a use-after-free bug. (CVE-2017-15649, Important) A vulnerability was found in the Linux kernel where the keyctlsetreqkeykeyring() function leaks the thread keyring. This allows an unprivileged local user to exhaust kernel memory and thus cause a DoS. (CVE-2017-7472, Moderate) Red Hat would like to thank Dmitry Vyukov of Google engineering for reporting CVE-2015-8539.Bug Fix(es): The kernel-rt packages have been upgraded to 3.10.0-693.15.1 source tree, which provides a number of bug fixes over the previous version. (BZ#1519506)
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2018:0152?
The severity of RHSA-2018:0152 is classified as important due to the potential for local privilege escalation.
How do I fix RHSA-2018:0152?
To fix RHSA-2018:0152, install the updated kernel-rt package version 3.10.0-693.17.1.rt56.636.el7.
What are the affected packages in RHSA-2018:0152?
The affected packages in RHSA-2018:0152 include various kernel-rt packages, such as kernel-rt, kernel-rt-debug, and kernel-rt-trace.
Is there a workaround for RHSA-2018:0152?
There is no official workaround provided for RHSA-2018:0152; patching the kernel is recommended.
When was the RHSA-2018:0152 advisory released?
The RHSA-2018:0152 advisory was released on February 1, 2018.