A non-prigileged user is able to mount a fuse filesystem on RHEL6 or 7 and crash a system if an application punches a hole in a file that does not end aligned to a page boundary.
Acknowledgments: Name: Miklos Szeredi (Red Hat)
Vladis, is this a Red Hat Kernel specific issue?
hei hai, Salvatore, yes, mostly. it appeared that rhel-6 and -7 are vulnerable, but rhel-alt is not. this means the flaw is reproduced with kernels from, at leat, 2.6.32 to 3.10, but not with 4.11. the upstream fix for this is commit 5a7203947a1d ("mm: teach truncate_inode_pages_range() to handle non page aligned ranges") which is in the upstream since v3.11-rc1.
Statement: This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 7 for ARM and Red Hat Enterprise Linux 7 for Power LE. This issue affects the versions of the Linux kernel as shipped with 6, 7 and Red Hat Enterprise MRG 2. Future updates for the respective releases may address this issue.
What is Red Hat Enterprise Linux 7 for ARM, Red Hat Enterprise Linux 7 for Power LE, and the "kernel-alt" package: The "kernel-alt" package as shipped with Red Hat Enterprise Linux 7 for ARM and Red Hat Enterprise Linux 7 for Power LE is an updated kernel intended to support new architectures not available at the time of Red Hat Enterprise Linux 7 original shipping. The new kernel version provided by the "kernel-alt" packages is based on upstream Linux kernel version 4.11. The offering is distributed with other updated packages, but most of the userspace is the standard Red Hat Enterprise Linux 7 Server RPM files. For more information please refer to: https://access.redhat.com/articles/3158541 https://access.redhat.com/articles/3158511
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2018:0676 https://access.redhat.com/errata/RHSA-2018:0676
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2018:1062 https://access.redhat.com/errata/RHSA-2018:1062
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2018:1854 https://access.redhat.com/errata/RHSA-2018:1854