# CVE-2022-49769: gfs2: Check sb_bsize_shift after reading superblock

Status: published. Published: 2025-05-01. Updated: 2026-11-05.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ b3b94faa5fe5968827ba0640ee9fba4b3e7f736e; < d6b1e8ea6f3418c3b461ad5a35cdc93c996b2c87 (affected, git); ≥ b3b94faa5fe5968827ba0640ee9fba4b3e7f736e; < 1ad197097343568066a8ffaa27ee7d0ae6d9f476 (affected, git); ≥ b3b94faa5fe5968827ba0640ee9fba4b3e7f736e; < 15c83fa0fd659dd9fbdc940a560b61236e876a80 (affected, git); ≥ b3b94faa5fe5968827ba0640ee9fba4b3e7f736e; < 8b6534c9ae9dba5489703a19d8ba6c8f2cfa33c2 (affected, git); ≥ b3b94faa5fe5968827ba0640ee9fba4b3e7f736e; < 5fa30be7ba81191b0a0c7239a89befc0c94286d5 (affected, git); ≥ b3b94faa5fe5968827ba0640ee9fba4b3e7f736e; < 28275a7c84d21c55ab3282d897f284d8d527173c (affected, git); ≥ b3b94faa5fe5968827ba0640ee9fba4b3e7f736e; < 16670534c7cff1acd918a6a5ec751b14e7436b76 (affected, git); ≥ b3b94faa5fe5968827ba0640ee9fba4b3e7f736e; < 670f8ce56dd0632dc29a0322e188cc73ce3c6b92 (affected, git). Source: CNA: Linux
- Linux / Linux: 2.6.19 (affected); ≥ 0; < 2.6.19 (unaffected, semver); ≥ 4.9.334; ≤ 4.9.* (unaffected, semver); ≥ 4.14.300; ≤ 4.14.* (unaffected, semver); ≥ 4.19.267; ≤ 4.19.* (unaffected, semver); ≥ 5.4.225; ≤ 5.4.* (unaffected, semver); ≥ 5.10.156; ≤ 5.10.* (unaffected, semver); ≥ 5.15.80; ≤ 5.15.* (unaffected, semver); ≥ 6.0.10; ≤ 6.0.* (unaffected, semver); ≥ 6.1; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.22% as of 2026-11-05; percentile 12.34%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/d6b1e8ea6f3418c3b461ad5a35cdc93c996b2c87 (CNA: Linux)

- https://git.kernel.org/stable/c/1ad197097343568066a8ffaa27ee7d0ae6d9f476 (CNA: Linux)

- https://git.kernel.org/stable/c/15c83fa0fd659dd9fbdc940a560b61236e876a80 (CNA: Linux)

- https://git.kernel.org/stable/c/8b6534c9ae9dba5489703a19d8ba6c8f2cfa33c2 (CNA: Linux)

- https://git.kernel.org/stable/c/5fa30be7ba81191b0a0c7239a89befc0c94286d5 (CNA: Linux)

- https://git.kernel.org/stable/c/28275a7c84d21c55ab3282d897f284d8d527173c (CNA: Linux)

- https://git.kernel.org/stable/c/16670534c7cff1acd918a6a5ec751b14e7436b76 (CNA: Linux)

- https://git.kernel.org/stable/c/670f8ce56dd0632dc29a0322e188cc73ce3c6b92 (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2022-49769; retrieved 2026-11-05; source updated 2026-11-05

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2022-49769; retrieved 2026-11-05; source updated Not reported

Revision: e76f90877decd5f5ae742ad8e1761c54cbc6157d73f367ba9016fc8d8a8d51be

Canonical: https://y2.dev/cve/CVE-2022-49769

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.