Review reviewHigh

CVE-2023-52804

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: fs/jfs: Add validity check for db_maxag and db_agpref Both db_maxag and db_agpref are used as the index of the db_agfree array, but there is currently no validity check for db_maxag and db_agpref, which can lead to errors. The following is related bug reported by Syzbot: UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:639:20 index 7936 is out of range for type 'atomic_t[128]' Add checking that the values of db_maxag and db_agpref are valid indexes for the db_agfree array.

CVSS
7.8
EPSS
0.26%
16.9% percentile
CISA KEV
Not listed
Published
2024.05.22
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: fs/jfs: Add validity check for db_maxag and db_agpref Both db_maxag and db_agpref are used as the index of the db_agfree array, but there is currently no validity check for db_maxag and db_agpref, which can lead to errors. The following is related bug reported by Syzbot: UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:639:20 index 7936 is out of range for type 'atomic_t[128]' Add checking that the values of db_maxag and db_agpref are valid indexes for the db_agfree array.

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < a0649e2dd4a3595b5595a29d0064d047c2fae2fb, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ce15b0f1a431168f07b1cc6c9f71206a2db5c809, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 32bd8f1cbcf8b663e29dd1f908ba3a129541a11b, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < c6c8863fb3f57700ab583d875adda04caaf2278a, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 1f74d336990f37703a8eee77153463d65b67f70e, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5013f8269887642cca784adc8db9b5f0b771533f, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < dca403bb035a565bb98ecc1dda5d30f676feda40, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 2323de34a3ae61a9f9b544c18583f71cea86721f, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 64933ab7b04881c6c18b21ff206c12278341c72e, >= 2.6.12, < 4.14.331, >= 4.15 < 4.19.300, >= 4.20 < 5.4.262, >= 5.5 < 5.10.202, >= 5.11 < 5.15.140, >= 5.16 < 6.1.64, >= 6.2 < 6.5.13, >= 6.6 < 6.6.3
Fixed versions
4.14.331, 4.19.300, 5.4.262, 5.10.202, 5.15.140, 6.1.64, 6.5.13, 6.6.3

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:H/A:H
CWE
CWE-129
CVE-2023-52804 — Linux Linux, linux kernel | SECUFOCUS NOW