CVE-2023-4385

What it actually does

NULL pointer dereference in dbFree within fs/jfs/jfs_dmap.c triggered by missing sanity check on JFS metadata, resulting in kernel panic.

Why it matters to the business

Local denial-of-service on Linux systems using the JFS filesystem, causing unplanned outages and potential loss of availability without remote exploitation or data compromise; low EPSS and non-KEV status indicate limited active threat but still requires attention on affected kernels published over three years ago.

How an attack unfolds

A local attacker with user privileges prepares or mounts a JFS filesystem containing malformed metadata that reaches dbFree without proper validation, dereferences a NULL pointer, and forces a kernel crash.

How to fix it

Update the Linux kernel to a version that includes the JFS sanity-check fix; if JFS is unnecessary, disable the module or avoid mounting JFS volumes entirely.

How to confirm the fix worked

Confirm the running kernel is newer than the vulnerable release, review kernel configuration for JFS support, and test mount/IO operations on sample JFS images to ensure no panic occurs.

Typical attack path

1. Obtain local shell or process execution rights on the target Linux system
2. Create or obtain a JFS-formatted image with invalid dmap structures
3. Mount the image or perform file operations that invoke dbFree
4. Trigger the NULL dereference to induce kernel panic and system reboot

How to detect it

Search system logs and kernel crash dumps for oops or panic entries referencing jfs_dmap.c or dbFree; correlate with recent JFS mount or filesystem access events from untrusted local processes.

What your security team should do

• Inventory all systems running JFS and schedule kernel upgrades
• Restrict local user capabilities on systems that must retain JFS
• Add JFS-related oops and panic patterns to monitoring rules
• Consider deprecating JFS in favor of supported filesystems where feasible