CVE-2022-49769 json
gfs2: Check sb_bsize_shift after reading superblock
published 2025-05-01 18 mo ago modified 2026-11-05 3 d ago also EUVD-2025-13008
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 4.9.334, 4.14.300, 4.19.267, 5.4.225, 5.10.156, 5.15.80, 6.0.10, 6.1
- linux Debian 14, Debian 13, Debian 12 6.0.10-1
debian advisories DEBIAN-CVE-2022-49769
- linux Ubuntu 18.04 LTS 4.15.0-206.217
- linux Ubuntu 20.04 LTS 5.4.0-144.161
- linux Ubuntu 22.04 LTS 5.15.0-67.74
- linux-aws Ubuntu 18.04 LTS 4.15.0-1151.164
- linux-aws Ubuntu 20.04 LTS 5.4.0-1097.105
- linux-aws Ubuntu 22.04 LTS 5.15.0-1031.35
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1101.110
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1030.37
ubuntu advisories UBUNTU-CVE-2022-49769
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.167.1
- kernel-syms SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +3 more 5.14.21-150400.24.167.1
- kernel-source SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +3 more 5.14.21-150400.24.167.1
- kernel-default SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +7 more 5.14.21-150400.24.167.1
- kernel-zfcpdump SLES 15 SP4-LTSS, Manager Server 4.3 5.14.21-150400.24.167.1
- kernel-obs-build SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.167.1
- kernel-default-base SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +5 more 5.14.21-150400.24.167.1.150400.24.84.1
- kernel-64kb SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS, SLE High Performance Computing 15 SP5-ESPOS 5.14.21-150500.55.110.1
suse advisories SUSE-SU-2025:02262-1SUSE-SU-2025:02173-1SUSE-SU-2025:01995-1SUSE-SU-2025:01983-1SUSE-SU-2025:01982-1SUSE-SU-2025:01966-1
- git.kernel.org/stable/c/d6b1e8ea6f3418c3b461ad5a35cdc93c996b2c87 commit
- git.kernel.org/stable/c/1ad197097343568066a8ffaa27ee7d0ae6d9f476 commit
- git.kernel.org/stable/c/15c83fa0fd659dd9fbdc940a560b61236e876a80 commit
- git.kernel.org/stable/c/8b6534c9ae9dba5489703a19d8ba6c8f2cfa33c2 commit
- git.kernel.org/stable/c/5fa30be7ba81191b0a0c7239a89befc0c94286d5 commit
- git.kernel.org/stable/c/28275a7c84d21c55ab3282d897f284d8d527173c commit
- git.kernel.org/stable/c/16670534c7cff1acd918a6a5ec751b14e7436b76 commit
- git.kernel.org/stable/c/670f8ce56dd0632dc29a0322e188cc73ce3c6b92 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-49769 updated cvss 3.3
kernel: gfs2: Check sb_bsize_shift after reading superblock
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/d6b1e8ea6f3418c3b461ad5a35cdc93c996b2c87
patch
-
git.kernel.org
/stable/c/1ad197097343568066a8ffaa27ee7d0ae6d9f476
patch
-
git.kernel.org
/stable/c/15c83fa0fd659dd9fbdc940a560b61236e876a80
patch
-
git.kernel.org
/stable/c/8b6534c9ae9dba5489703a19d8ba6c8f2cfa33c2
patch
-
git.kernel.org
/stable/c/5fa30be7ba81191b0a0c7239a89befc0c94286d5
patch
-
git.kernel.org
/stable/c/28275a7c84d21c55ab3282d897f284d8d527173c
patch
-
git.kernel.org
/stable/c/16670534c7cff1acd918a6a5ec751b14e7436b76
patch
-
git.kernel.org
/stable/c/670f8ce56dd0632dc29a0322e188cc73ce3c6b92
patch
Sources
- CVE List CVE-2022-49769
- NVD CVE-2022-49769
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.