Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-52804

fs/jfs: Add validity check for db_maxag and db_agpref

High7.8EPSS 0.26%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Scores

CVSS scores of CVE-2023-52804, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.26% · top 83% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Weakness

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a0649e2dd4a3595b5595a29d0064d047c2fae2fb
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ce15b0f1a431168f07b1cc6c9f71206a2db5c809
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 32bd8f1cbcf8b663e29dd1f908ba3a129541a11b
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c6c8863fb3f57700ab583d875adda04caaf2278a
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1f74d336990f37703a8eee77153463d65b67f70e
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5013f8269887642cca784adc8db9b5f0b771533f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < dca403bb035a565bb98ecc1dda5d30f676feda40
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2323de34a3ae61a9f9b544c18583f71cea86721f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 64933ab7b04881c6c18b21ff206c12278341c72e
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 4.14.331 – ≤ 4.14.*
    • unaffected 4.19.300 – ≤ 4.19.*
    • unaffected 5.4.262 – ≤ 5.4.*
    • unaffected 5.10.202 – ≤ 5.10.*
    • unaffected 5.15.140 – ≤ 5.15.*
    • unaffected 6.1.64 – ≤ 6.1.*
    • unaffected 6.5.13 – ≤ 6.5.*
    • unaffected 6.6.3 – ≤ 6.6.*
    • unaffected 6.7 – ≤ *

References (9)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-52804 badge
[![CVE-2023-52804](https://trackcve.app/badge/CVE-2023-52804.svg)](https://trackcve.app/cve/CVE-2023-52804)

Record last updated .