gfs2: Check sb_bsize_shift after reading superblock
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b3b94faa5fe5968827ba0640ee9fba4b3e7f736e · < 28275a7c84d21c55ab3282d897f284d8d527173c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gfs2: Check sb_bsize_shift after reading superblock
Fuzzers like to scribble over sb_bsize_shift but in reality it's very unlikely that this field would be corrupted on its own. Nevertheless it should be checked to avoid the possibility of messy mount errors due to bad calculations. It's always a fixed value based on the block size so we can just check that it's the expected value.
Tested with:
mkfs.gfs2 -O -p lock_nolock /dev/vdb for i in 0 -1 64 65 32 33; do gfs2_edit -p sb field sb_bsize_shift $i /dev/vdb mount /dev/vdb /mnt/test && umount /mnt/test done
Before this patch we get a withdraw after
[ 76.413681] gfs2: fsid=loop0.0: fatal: invalid metadata block [ 76.413681] bh = 19 (type: exp=5, found=4) [ 76.413681] function = gfs2_meta_buffer, file = fs/gfs2/meta_io.c, line = 492
and with UBSAN configured we also get complaints like
From the CVE record · Linux
The Linux kernel's GFS2 code did not validate sb_bsize_shift after reading a filesystem superblock. Mounting a GFS2 filesystem with a corrupted value could cause invalid calculations, filesystem withdrawal, and shift-out-of-bounds reports. The input does not specify a network attack path or authentication requirements.
Engineers running Linux kernels with GFS2 support should check their versions; affected versions are not specified.