Affected: AlmaLinux:8: kernel-tools-libs-devel

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

Security Fix(es):

* kernel: Integer overflow in Intel(R) Graphics Drivers (CVE-2020-12362)

* kernel: memory leak in sof_set_get_large_ctrl_data() function in sound/soc/sof/ipc.c (CVE-2019-18811)

* kernel: use-after-free caused by a malicious USB device in the drivers/usb/misc/adutux.c driver (CVE-2019-19523)

* kernel: use-after-free bug caused by a malicious USB device in the drivers/usb/misc/iowarrior.c driver (CVE-2019-19528)

* kernel: possible out of bounds write in kbd_keycode of keyboard.c (CVE-2020-0431)

* kernel: DoS by corrupting mountpoint reference counter (CVE-2020-12114)

* kernel: use-after-free in usb_sg_cancel function in drivers/usb/core/message.c (CVE-2020-12464)

* kernel: buffer uses out of index in ext3/4 filesystem (CVE-2020-14314)

* kernel: Use After Free vulnerability in cgroup BPF component (CVE-2020-14356)

* kernel: NULL pointer dereference in serial8250_isa_init_ports function in drivers/tty/serial/8250/8250_core.c (CVE-2020-15437)

* kernel: umask not applied on filesystem without ACL support (CVE-2020-24394)

* kernel: TOCTOU mismatch in the NFS client code (CVE-2020-25212)

* kernel: incomplete permission checking for access to rbd devices (CVE-2020-25284)

* kernel: race condition between hugetlb sysctl handlers in mm/hugetlb.c (CVE-2020-25285)

* kernel: improper input validation in ppp_cp_parse_cr function leads to memory corruption and read overflow…

A flaw was found in the Linux kernel’s implementation of MIDI, where an attacker with a local account and the permissions to issue ioctl commands to midi devices could trigger a use-after-free issue. A write to this specific memory while freed and before use causes the flow of execution to change and possibly allow for memory corruption or privilege escalation. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

A flaw was found in the Linux kernels implementation of MIDI (kernel 5.7-rc6), where an attacker with a local account and the permissions to issue an ioctl commands to midi devices, could trigger a use-after-free. A write to this specific memory while freed and before use could cause the flow of execution to change and possibly allow for memory corruption or privilege escalation.

Affected: openEuler:20.03-LTS: kernel

The Linux Kernel, the operating system core itself. Security Fix(es): In drivers/target/target_core_xcopy.c in the Linux kernel before 5.10.7, insufficient identifier checking in the LIO SCSI target code can be used by remote attackers to read or write files via directory traversal in an XCOPY request, aka CID-2896c93811e3. For example, an attack can occur over a network if the attacker has access to one iSCSI LUN. The attacker gains control over file access because I/O operations are proxied via an attacker-selected backstore.(CVE-2020-28374) An issue was discovered in Xen through 4.14.x. Some OSes (such as Linux, FreeBSD, and NetBSD) are processing watch events using a single thread. If the events are received faster than the thread is able to handle, they will get queued. As the queue is unbounded, a guest may be able to trigger an OOM in the backend. All systems with a FreeBSD, Linux, or NetBSD (any version) dom0 are vulnerable.(CVE-2020-29568) In the nl80211_policy policy of nl80211.c, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not required for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-119770583(CVE-2020-27068) A flaw was found in the Linux kernels implementation of MIDI, where an attacker with a local account and the permissions to issue an ioctl commands to midi devices, could trigger a use-afte…

Security update for the Linux Kernel

kernel: use-after-free caused by a malicious USB device in the drivers/usb/misc/adutux.c driver kernel: use-after-free bug caused by a malicious USB device in the drivers/usb/misc/iowarrior.c driver kernel: possible out of bounds write in kbd_keycode of keyboard.c kernel: NULL pointer dereferences in ov511_mode_init_regs and ov518_mode_init_regs in drivers/media/usb/gspca/ov519.c kernel: DoS by corrupting mountpoint reference counter kernel: Integer overflow in Intel(R) Graphics Drivers kernel: Improper input validation in some Intel(R) Graphics Drivers kernel: Null pointer dereference in some Intel(R) Graphics Drivers kernel: use-after-free in usb_sg_cancel function in drivers/usb/core/message.c kernel: buffer uses out of index in ext3/4 filesystem kernel: Use After Free vulnerability in cgroup BPF component kernel: NULL pointer dereference in serial8250_isa_init_ports function in drivers/tty/serial/8250/8250_core.c kernel: umask not applied on filesystem without ACL support kernel: TOCTOU mismatch in the NFS client code kernel: incomplete permission checking for access to rbd devices kernel: race condition between hugetlb sysctl handlers in mm/hugetlb.c kernel: improper input validation in ppp_cp_parse_cr function leads to memory corruption and read overflow kernel: perf_event_parse_addr_filter memory kernel: use-after-free in kernel midi subsystem kernel: child process is able to access parent mm through hfi dev file handle kernel: slab-out-of-bounds read in fbcon kernel:…

Security update for the Linux Kernel

Affected: Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:16.04:LTS: linux, Ubuntu:16.04:LTS: linux-aws, Ubuntu:16.04:LTS: linux-aws-hwe, Ubuntu:16.04:LTS: linux-azure, Ubuntu:16.04:LTS: linux-gcp, Ubuntu:16.04:LTS: linux-hwe and 56 more

A flaw was found in the Linux kernel’s implementation of MIDI, where an attacker with a local account and the permissions to issue ioctl commands to midi devices could trigger a use-after-free issue. A write to this specific memory while freed and before use causes the flow of execution to change and possibly allow for memory corruption or privilege escalation. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.