gfs2 in the Linux kernel 2.6.18, and possibly other versions, does not properly handle when the gfs2_quota struct occupies two separate pages, which allows local users to cause a denial of service (kernel panic) via certain manipulations that cause an out-of-bounds write, as demonstrated by writing from an ext3 file system to a gfs2 file system.

gfs2 in the Linux kernel 2.6.18, and possibly other versions, does not properly handle when the gfs2_quota struct occupies two separate pages, which allows local users to cause a denial of service (kernel panic) via certain manipulations that cause an out-of-bounds write, as demonstrated by writing from an ext3 file system to a gfs2 file system.

kernel-debug-4.8.13-1.1 on GA media

kernel: untangle the do_mremap() kernel: futex: Handle user space corruption gracefully kernel: NFS: Fix an Oops when truncating a file kernel: fix LOOKUP_FOLLOW on automount "symlinks" kernel: sctp: crash due to malformed SCTPChunkInit packet kernel: tipc: Fix oops on send prior to entering networked mode kernel: gfs2 buffer overflow kernel: keyrings: find_keyring_by_name() can gain the freed keyring kernel: GFS2: The setflags ioctl() doesn't check file ownership