In the Linux kernel, the ext4 filesystem code incorrectly publishes a jinode pointer before it is fully initialized. A reader can see a non‑NULL jinode while the corresponding VFS inode still has no mapping, leading the fast commit flush path to dereference an uninitialized pointer and crash. The resulting kernel panic manifests as a denial of service for the entire system.

The vulnerability is present in any Linux kernel that includes ext4 before the fix was applied. No specific version ranges are listed in the data, so all older kernels that contain the described code are potentially affected.

The lack of an EPSS score and absence from the CISA KEV catalog means exploitation probability is unknown, but the impact is high because a kernel panic brings the system offline. The creation of the fault requires a write, sync, or fsync operation on an ext4 filesystem, which can be triggered by a local user or escalated attacker. Accordingly, the risk is inferred to be moderate to high for impacted hosts.