ext4 filesystem

In the Linux kernel’s ext4 filesystem, a small logic change has been turned into a security-relevant reliability fix: the code path that reads inline data now avoids a kernel-panic-style BUG_ON() when the inline payload is larger than a page. Instead of crashing the system, the kernel now logs...

The Linux kernel’s ext4 filesystem is now facing a newly published CVE that closes off an unsupported mount configuration before it can do damage. CVE-2026-31447 addresses a specific mismatch between bigalloc and a nonzero s_first_data_block, and the fix is simple in spirit: refuse to mount a...

Linux administrators received a fresh reminder this week that ext4’s maturity does not make it immune to memory-safety bugs. CVE-2026-31449 is a slab-out-of-bounds read in the Linux kernel’s ext4 extent-tree logic, and it appears in a code path that corrects index entries after leaf extents are...

CVE-2026-31449 is a reminder that some of the most consequential Linux kernel bugs are not flashy exploit chains, but narrow trust failures inside core filesystem machinery. In this case, the flaw sits in ext4’s extent-tree correction logic, where an unchecked pointer can drift past the end of...

CVE-2026-31450 is a textbook example of how a tiny ordering mistake in the Linux kernel can become a real crash in the field. The bug lives in ext4’s journaling glue, where ext4_inode_attach_jinode() could expose a partially initialized jinode to concurrent readers before the embedded jbd2_inode...

In the Linux kernel’s ext4 filesystem, a newly published vulnerability, CVE-2026-31448, exposes a failure path that can leave the filesystem spinning in an infinite loop while holding critical locks. The issue is tied to how ext4 handles extent-tree insertion failures during mkdir and mknod, and...