CVE-2025-38697

What it actually does

Missing upper bound check on tree index computation in dbAllocAG allows out-of-bounds memory access when JFS filesystem metadata is corrupted, enabling memory corruption.

Why it matters to the business

Local attackers on Linux systems using JFS can achieve full system compromise via privilege escalation, increasing risk of data theft or persistent unauthorized access on affected servers and containers.

How an attack unfolds

An attacker with local access crafts or corrupts JFS metadata to force dbAllocAG to use an out-of-bounds tree index, resulting in invalid memory operations that are leveraged to execute arbitrary code and escalate privileges.

How to fix it

Update the Linux kernel to include commit 5bdb9553fb134fd52ec208a8b378120670f6e784 or later; rebuild and deploy the patched kernel on all systems using JFS.

How to confirm the fix worked

Confirm the fix commit is present in the running kernel source tree and verify that intentionally corrupted JFS metadata no longer triggers out-of-bounds access or crashes during allocation.

Typical attack path

1. Gain local user access on target system
2. Corrupt or manipulate JFS filesystem metadata structures
3. Trigger allocation operations invoking dbAllocAG
4. Exploit resulting out-of-bounds access for kernel-level code execution

How to detect it

Review kernel logs for JFS-related errors, oops messages, or panics referencing dbAllocAG or tree index calculations; inspect for signs of unexpected filesystem metadata corruption.

What your security team should do

• Prioritize kernel upgrade to the fixed commit on all JFS-using systems
• Audit for JFS usage and migrate workloads to alternative filesystems where feasible
• Enable filesystem integrity monitoring to detect metadata corruption early