Review reviewHigh

CVE-2022-50567

Linux

In the Linux kernel, the following vulnerability has been resolved: fs: jfs: fix shift-out-of-bounds in dbAllocAG Syzbot found a crash : UBSAN: shift-out-of-bounds in dbAllocAG. The underlying bug is the missing check of bmp->db_agl2size. The field can be greater than 64 and trigger the shift-out-of-bounds. Fix this bug by adding a check of bmp->db_agl2size in dbMount since this field is used in many following functions. The upper bound for this field is L2MAXL2SIZE - L2MAXAG, thanks for the help of Dave Kleikamp. Note that, for maintenance, I reorganized error handling code of dbMount.

CVSS
7.8
EPSS
0.16%
5.66% percentile
CISA KEV
Not listed
Published
2025.10.22
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.16%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: fs: jfs: fix shift-out-of-bounds in dbAllocAG Syzbot found a crash : UBSAN: shift-out-of-bounds in dbAllocAG. The underlying bug is the missing check of bmp->db_agl2size. The field can be greater than 64 and trigger the shift-out-of-bounds. Fix this bug by adding a check of bmp->db_agl2size in dbMount since this field is used in many following functions. The upper bound for this field is L2MAXL2SIZE - L2MAXAG, thanks for the help of Dave Kleikamp. Note that, for maintenance, I reorganized error handling code of dbMount.

Affected product and versions

Product
Linux
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d3b486946a4e62c7ef6023f7d9c1d049051384ba, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 3115313cf03113e87c87adee18ee49a20bbdb9ba, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < eea87acb6027be3dd4d3c57186bb22800d57fdda, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 359616ce587e524107730504891afa4b1a8be58c, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 3e997e4ce8ae7ab89d72334120f6aee49c5bbdbd, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0536f76a2bca83d1a3740517ba22cc93a44b3099, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 2c575c8905f7a8b32d5611b91856b69bac2a5bf1, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 67973caae78e21ee46a7281aaa8ca364eb9c444f, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 898f706695682b9954f280d95e49fa86ffa55d08, >= 2.6.12
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available