# CVE-2024-47723: jfs: fix out-of-bounds in dbNextAG() and diAlloc()

> A local attacker can trigger an out-of-bounds read in the JFS filesystem driver, potentially causing a system crash or arbitrary code execution.

- **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 Oct 2024
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-51126, AZL-51297, BELL-CVE-2024-47723, DEBIAN-CVE-2024-47723, GHSA-f3wc-386p-mwc3, UBUNTU-CVE-2024-47723

## What is CVE-2024-47723?

CVE-2024-47723 is a high-severity memory corruption vulnerability in Linux kernel, published on 21 Oct 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:

jfs: fix out-of-bounds in dbNextAG() and diAlloc()

In dbNextAG() , there is no check for the case where bmp->db_numag is
greater or same than MAXAG due to a polluted image, which causes an
out-of-bounds. Therefore, a bounds check should be added in dbMount().

And in dbNextAG(), a check for the case where agpref is greater than
bmp->db_numag should be added, so an out-of-bounds exception should be
prevented.

Additionally, a check for the case where agno is greater or same than
MAXAG should be added in diAlloc() to prevent out-of-bounds.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2024-47723?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-47723?

Apply the vendor's patch.

## Is CVE-2024-47723 being exploited?

There is no known exploitation of CVE-2024-47723 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-2024-47723 and fix it if it is affected.

What it is: CVE-2024-47723 is a high-severity memory corruption vulnerability in Linux kernel, published on 21 Oct 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-2024-47723 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-2024-47723/ (Markdown: https://insights.sbomify.com/CVE-2024-47723/index.md)
```

## Sources

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

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