-
PSBM-96719
Data corruption in the EXT4 file system when truncating the extent index blocks.
-
PSBM-95177
Kernel complained about busy inodes after unmount of NFS shares and crashed in certain cases.
-
PSBM-97012
memcg: race condition between reparenting and kmem uncharging.
It was discovered that a race condition was possible between kmem uncharging and mem_cgroup_reparent_charges(). A kernel warning would be triggered as a result.
-
PSBM-97905
Kernel crashed in down_read() when a FUSE file system was exported via NFS.
-
CVE-2019-14835
vhost-net: guest to host kernel escape during migration
A buffer overflow vulnerability was found in the networking virtualization functionality (vhost-net) that could be abused during live migration of virtual machines. A privileged guest user may pass descriptors with invalid length to the host when live migration is underway to crash the host kernel or, potentially, escalate their privileges on the host.
https://bugzilla.redhat.com/show_bug.cgi?id=1750727
-
CVE-2019-11810
megaraid_sas: potential kernel crash due to a NULL pointer dereference in megasas_free_cmds().
A flaw was found in 'megaraid_sas' kernel module. NULL pointer dereference can occur in megasas_free_cmds() function due incorrect error handling in megasas_alloc_cmds(). An attacker could exploit this to trigger a kernel crash.
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-11810
-
PSBM-96533
The warning in mem_cgroup_reparent_charges() was triggered too early and too often in certain cases.
-
PSBM-96262
kvm: potential system hang due to an error in mmu_shrink_scan().
-
CVE-2018-16871
nfs: NULL pointer dereference due to an anomalized NFS message sequence.
An attacker, who is able to mount an exported NFS filesystem, is able to trigger a null pointer dereference by using an invalid NFS sequence. This can panic the machine and deny access to the NFS server. Any outstanding disk writes to the NFS server will be lost.
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16871
-
VSTOR-21044
fuse_kio_pcs: kernel crash in pcs_sockio_xmit().
-
PSBM-96057
Processes could get stuck in copy_net_ns() forever.
-
PSBM-95815
vziolimit: kernel crash due to a division by zero in throttle_charge().
-
VSTOR-24241
mem_cgroup_reparent_charges() could get stuck while holding cgroup_mutex and make the whole system hang.
-
PSBM-95700
Kernel crash in memcg_inc_ws_activate().
It was discovered that a race could happen between removal of memcg and workingset_refault() running in parallel. This could result in a kernel crash in memcg_inc_ws_activate().
-
PSBM-95077
kvm: inefficient memory shrinking for VMs.
It was discovered that a node with dozens of CPU cores, lots of RAM and many VMs running could get into a situation when almost all CPU cores were busy in mmu_shrink_scan(). This could happen because memory shrinking was done under kvm_lock spinlock and only for one VM at a time. All CPU cores but one just waited for kvm_lock in such cases, while the last one was busy with the actual memory shrinking for a VM.
-
PSBM-94882
fuse_kio_pcs: latency was calculated incorrectly.
It was found that the in-kernel implementation of Virtuozzo Storage client stored latency values in milliseconds rather than in microseconds, resulting in bogus statistics data.
-
CVE-2019-11477
tcp: integer overflow while processing SACK blocks allows remote denial of service.
An integer overflow was found in the way the Linux kernel's networking subsystem processed TCP Selective Acknowledgment (SACK) segments. While processing SACK segments, the Linux kernel's socket buffer (SKB) data structure becomes fragmented. Each fragment is about TCP maximum segment size (MSS) bytes. To efficiently process SACK blocks, the Linux kernel merges multiple fragmented SKBs into one, potentially overflowing the variable holding the number of segments. A remote attacker could use this flaw to crash the Linux kernel by sending a crafted sequence of SACK segments on a TCP connection with small value of TCP MSS, resulting in a denial of service.
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-11477
-
VSTOR-23689
Processes could hang while closing a file located on the storage cluster.
-
VSTOR-22575
OOM killer would kill tasks from cgroups without memory guarantees first.
If the amount of free memory is low, OOM killer would kill the tasks from cgroups without memory guarantees first. However, it seems more reasonable to kill the tasks from cgroups exceeding their guarantees the most.
-
PSBM-94270
ploop: kernel crash in ploop_congested().
-
PSBM-93988
ext4: inode tables created during online resize were not zeroed.
It was discovered that inode tables created during online resize of an ext4 filesystem were not zeroed after that. This could potentially result in lower performance of the filesystem.
-
PSBM-94429
Windows Server 2016 Essentials failed to install into a QEMU VM with disabled PMU.
It was found that if no PMU counters were exposed to guest, KVM skipped the whole remaining PMU-related initialization, including filling of LBR-related data. As it turned out, Windows Server 2016 Essentials tried to access these data during the installation and failed to install as a result.
-
PSBM-94727
ploop: 'pcompact' could hang if run simultaneously with 'ploop-balloon status'
-
PSBM-94535
Memory leak in the implementation of IPv4 routing.
It was discovered that a certain sequence of operations related to IPv4 routing could trigger a kernel memory leak. An attacker could potentially exploit that from a container to cause a denial of service.
-
PSBM-94398
Freeing of a memory cgroup took longer than needed in certain cases.
-
PSBM-94269
Kernel crash in memcg_css_release_check_kmem().
It was found that the memcg ID number of a cgroup was released earlier than needed and could then be reused by a different cgroup. As a result, certain reference counters could be corrupted, leading to a kernel crash in memcg_css_release_check_kmem().
-
VSTOR-22272
I/O errors were reported after a successful replacement of the ploop images.
-
VSTOR-22414
'ploop replace' did not clear 'abort' flag.
It was found that if a ploop image was revoked and then replaced using 'ploop replace', 'abort' flag was not cleared. As a result, subsequent I/O operations would fail.