CVE-2023-54069
Integer Overflow Bug in Linux Kernel ext4 Causes Kernel Panic
Publication date: 2025-12-24
Last updated on: 2025-12-24
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a bug in the Linux kernel's ext4 filesystem code, specifically in the ext4_mb_new_inode_pa() function. It occurs due to an integer overflow when calculating the end position of ext4_free_extent, which can cause the computed end to wrap around to zero incorrectly. This leads to a kernel BUG being triggered, causing a crash or invalid opcode error during filesystem operations involving extent allocation.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash or become unstable when performing certain filesystem operations on ext4 partitions. This could lead to data loss, system downtime, or corruption of the filesystem, impacting system reliability and availability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel BUG messages related to ext4_mb_new_inode_pa() in the kernel logs. You can check for such BUGs using commands like 'dmesg | grep ext4_mb_new_inode_pa' or 'journalctl -k | grep ext4_mb_new_inode_pa'. Additionally, reproducing the issue involves filesystem operations on ext4 as shown in the example commands: mkfs.ext4, mount, fallocate, fsstress, and xfs_io, but these are more for testing than detection.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this ext4 overflow bug is fixed, as the issue is resolved by refactoring the ext4_mb_new_inode_pa() logic. Until then, avoid running workloads that heavily stress ext4 allocation paths with large fallocate operations or fsstress tools that might trigger the bug.