# CVE-2023-52804: fs/jfs: Add validity check for db_maxag and db_agpref

> A missing validity check in the Linux kernel JFS filesystem allows out-of-bounds array access, potentially causing a system crash.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2023-52804, DEBIAN-CVE-2023-52804, GHSA-xhh8-8jq9-8vf6, UBUNTU-CVE-2023-52804

## What is CVE-2023-52804?

CVE-2023-52804 is a high-severity vulnerability in Linux kernel, published on 21 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2023-52804?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-52804?

Apply the vendor's patch.

## Is CVE-2023-52804 being exploited?

There is no known exploitation of CVE-2023-52804 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52804 and fix it if it is affected.

What it is: CVE-2023-52804 is a high-severity vulnerability in Linux kernel, published on 21 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52804 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-52804/ (Markdown: https://insights.sbomify.com/CVE-2023-52804/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-52804
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-52804
- OSV: https://osv.dev/vulnerability/CVE-2023-52804

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-52804/
Summaries are generated and may contain mistakes; the official description above is the record.