Moderate: kernel-rt security update
Important: kernel-rt security update
Important: kernel-rt security update
Moderate: kernel security update
Important: kernel-rt security update
Moderate: tuned security update
Important: kernel-rt security update
Important: kernel-rt security update
Important: kernel-rt security and bug fix update
Important: kernel-rt security update
Important: kernel-rt security update
Important: kernel-rt security update
Important: kernel-rt security update
Important: kernel-rt security and bug fix update
Important: kernel-rt security and bug fix update
Important: kernel-rt security and bug fix update
Important: kernel-rt security and bug fix update
Important: kernel-rt security and bug fix update
A flaw was found in the Linux kernel. A memory leak in the ccp-ops crypto driver can allow attackers to cause a denial of service. This vulnerability is similar with the older CVE-2019-18808. The highest threat from this vulnerability is to system availability.
A local user can trigger a flaw in the Linux kernel's handling of key lookups in the keychain subsystem.
The keyrejectandlink() function contains an error in which a key-lookup can fail and in an attempt to cache the failed lookup may attempt to free memory which can still be in use.
This could crash the system or at worse free a memory block which would then be re-used by another kernel mechanism causing a user after free.
Product bug:
https://bugzilla.redhat.com/showbug.cgi?id=1341352
Upstream patch:
https://www.spinics.net/lists/linux-kernel-janitors/msg26069.html
A flaw was found in the kernel-rt in which an attacker could submit a specially crafted ICMP echo request which can trigger a sysrq function based on values in the ICMP packet.
This feature was introduced in the kernel-rt only and is not shipping with standard Red Hat Enterprise Linux kernels.
Remote attacker could exploit this feature using bruteforce to submit arbitrary SysRq commands.
Resources: https://www.kernel.org/pub/linux/kernel/projects/rt/4.4/patch-4.4.7-rt16.patch.gz
Upstream discussion: https://lwn.net/Articles/448790/
CVE request: http://seclists.org/oss-sec/2016/q2/349