Review reviewHigh

CVE-2023-53222

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: jfs: jfs_dmap: Validate db_l2nbperpage while mounting In jfs_dmap.c at line 381, BLKTODMAP is used to get a logical block number inside dbFree(). db_l2nbperpage, which is the log2 number of blocks per page, is passed as an argument to BLKTODMAP which uses it for shifting. Syzbot reported a shift out-of-bounds crash because db_l2nbperpage is too big. This happens because the large value is set without any validation in dbMount() at line 181. Thus, make sure that db_l2nbperpage is correct while mounting. Max number of blocks...

CVSS
7.1
EPSS
0.15%
5.01% percentile
CISA KEV
Not listed
Published
2025.09.16
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.15%
Technical severityCVSS 7.1

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: jfs: jfs_dmap: Validate db_l2nbperpage while mounting In jfs_dmap.c at line 381, BLKTODMAP is used to get a logical block number inside dbFree(). db_l2nbperpage, which is the log2 number of blocks per page, is passed as an argument to BLKTODMAP which uses it for shifting. Syzbot reported a shift out-of-bounds crash because db_l2nbperpage is too big. This happens because the large value is set without any validation in dbMount() at line 181. Thus, make sure that db_l2nbperpage is correct while mounting. Max number of blocks...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 8c1efe3f74a7864461b0dff281c5562154b4aa8e, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ef5c205b6e6f8d1f18ef0b4a9832b1b5fa85f7f2, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < a4855aeb13e4ad1f23e16753b68212e180f7d848, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 47b7eaae08e8b2f25bdf37bc14d21be090bcb20f, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < de984faecddb900fa850af4df574a25b32bb93f5, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < c7feb54b113802d2aba98708769d3c33fb017254, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 2a03c4e683d33d17b667418eb717b13dda1fac6b, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 11509910c599cbd04585ec35a6d5e1a0053d84c1, >= 2.6.12, < 4.14.322, >= 4.15 < 4.19.291, >= 4.20 < 5.4.251, >= 5.5 < 5.10.188, >= 5.11 < 5.15.121, >= 5.16 < 6.1.40, >= 6.2 < 6.4.5
Fixed versions
4.14.322, 4.19.291, 5.4.251, 5.10.188, 5.15.121, 6.1.40, 6.4.5

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel 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:N/A:H
CWE
CWE-125
CVE-2023-53222 — Linux Linux, linux kernel | SECUFOCUS NOW