CVE-2022-49769
published 2025-05-01CVE-2022-49769: In the Linux kernel, the following vulnerability has been resolved: gfs2: Check sb_bsize_shift after reading superblock Fuzzers like to scribble over…
PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
10.9th percentile
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
[ 76.373395] UBSAN: shift-out-of-bounds in fs/gfs2/ops_fstype.c:295:19
[ 76.373815] shift exponent 4294967287 is too large for 64-bit type 'long unsigned int'
After the patch, these complaints don't appear, mount fails immediately
and we get an explanation in dmesg.
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.10-1 (bookworm) | linux 6.0.10-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= b3b94faa5fe5968827ba0640ee9fba4b3e7f736e < d6b1e8ea6f3418c3b461ad5a35cdc93c996b2c87 | d6b1e8ea6f3418c3b461ad5a35cdc93c996b2c87 |
| linux | linux | >= b3b94faa5fe5968827ba0640ee9fba4b3e7f736e < 1ad197097343568066a8ffaa27ee7d0ae6d9f476 | 1ad197097343568066a8ffaa27ee7d0ae6d9f476 |
| linux | linux | >= b3b94faa5fe5968827ba0640ee9fba4b3e7f736e < 15c83fa0fd659dd9fbdc940a560b61236e876a80 | 15c83fa0fd659dd9fbdc940a560b61236e876a80 |
| linux | linux | >= b3b94faa5fe5968827ba0640ee9fba4b3e7f736e < 8b6534c9ae9dba5489703a19d8ba6c8f2cfa33c2 | 8b6534c9ae9dba5489703a19d8ba6c8f2cfa33c2 |
| linux | linux | >= b3b94faa5fe5968827ba0640ee9fba4b3e7f736e < 5fa30be7ba81191b0a0c7239a89befc0c94286d5 | 5fa30be7ba81191b0a0c7239a89befc0c94286d5 |
| linux | linux | >= b3b94faa5fe5968827ba0640ee9fba4b3e7f736e < 28275a7c84d21c55ab3282d897f284d8d527173c | 28275a7c84d21c55ab3282d897f284d8d527173c |
| linux | linux | >= b3b94faa5fe5968827ba0640ee9fba4b3e7f736e < 16670534c7cff1acd918a6a5ec751b14e7436b76 | 16670534c7cff1acd918a6a5ec751b14e7436b76 |
| linux | linux | >= b3b94faa5fe5968827ba0640ee9fba4b3e7f736e < 670f8ce56dd0632dc29a0322e188cc73ce3c6b92 | 670f8ce56dd0632dc29a0322e188cc73ce3c6b92 |
| linux | linux_kernel | < 4.9.334 | 4.9.334 |
| linux | linux_kernel | >= 0 < 5.10.158-1 | 5.10.158-1 |
| linux | linux_kernel | >= 0 < 6.0.10-1 | 6.0.10-1 |
| linux | linux_kernel | >= 0 < 6.0.10-1 | 6.0.10-1 |
| linux | linux_kernel | >= 0 < 6.0.10-1 | 6.0.10-1 |
| linux | linux_kernel | >= 4.10 < 4.14.300 | 4.14.300 |
| linux | linux_kernel | >= 4.15 < 4.19.267 | 4.19.267 |
| linux | linux_kernel | >= 4.20 < 5.4.225 | 5.4.225 |
| linux | linux_kernel | >= 5.11 < 5.15.80 | 5.15.80 |
| linux | linux_kernel | >= 5.16 < 6.0.10 | 6.0.10 |
| linux | linux_kernel | >= 5.5 < 5.10.156 | 5.10.156 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-22ff-fvm7-6wj7: In the Linux kernel, the following vulnerability has been resolved:
gfs2: Check sb_bsize_shift after reading superblock
Fuzzers like to scribble ove
ghsa_unreviewed·2025-05-01
CVE-2022-49769 [MEDIUM] GHSA-22ff-fvm7-6wj7: In the Linux kernel, the following vulnerability has been resolved:
gfs2: Check sb_bsize_shift after reading superblock
Fuzzers like to scribble ove
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]
OSV
CVE-2022-49769: In the Linux kernel, the following vulnerability has been resolved: gfs2: Check sb_bsize_shift after reading superblock Fuzzers like to scribble over
osv·2025-05-01·CVSS 5.5
CVE-2022-49769 [MEDIUM] CVE-2022-49769: In the Linux kernel, the following vulnerability has been resolved: gfs2: Check sb_bsize_shift after reading superblock Fuzzers like to scribble over
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] functi
Red Hat
kernel: gfs2: Check sb_bsize_shift after reading superblock
vendor_redhat·2025-05-01·CVSS 5.5
CVE-2022-49769 [MEDIUM] kernel: gfs2: Check sb_bsize_shift after reading superblock
kernel: gfs2: Check sb_bsize_shift after reading superblock
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
[
Debian
CVE-2022-49769: linux - In the Linux kernel, the following vulnerability has been resolved: gfs2: Check...
vendor_debian·2022·CVSS 5.5
CVE-2022-49769 [MEDIUM] CVE-2022-49769: linux - In the Linux kernel, the following vulnerability has been resolved: gfs2: Check...
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] functi
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/15c83fa0fd659dd9fbdc940a560b61236e876a80https://git.kernel.org/stable/c/16670534c7cff1acd918a6a5ec751b14e7436b76https://git.kernel.org/stable/c/1ad197097343568066a8ffaa27ee7d0ae6d9f476https://git.kernel.org/stable/c/28275a7c84d21c55ab3282d897f284d8d527173chttps://git.kernel.org/stable/c/5fa30be7ba81191b0a0c7239a89befc0c94286d5https://git.kernel.org/stable/c/670f8ce56dd0632dc29a0322e188cc73ce3c6b92https://git.kernel.org/stable/c/8b6534c9ae9dba5489703a19d8ba6c8f2cfa33c2https://git.kernel.org/stable/c/d6b1e8ea6f3418c3b461ad5a35cdc93c996b2c87
2025-05-01
Published