CVE-2023-53101
published 2025-05-02CVE-2023-53101: In the Linux kernel, the following vulnerability has been resolved: ext4: zero i_disksize when initializing the bootloader inode If the boot loader inode has…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.19%
8.9th percentile
In the Linux kernel, the following vulnerability has been resolved:
ext4: zero i_disksize when initializing the bootloader inode
If the boot loader inode has never been used before, the
EXT4_IOC_SWAP_BOOT inode will initialize it, including setting the
i_size to 0. However, if the "never before used" boot loader has a
non-zero i_size, then i_disksize will be non-zero, and the
inconsistency between i_size and i_disksize can trigger a kernel
warning:
WARNING: CPU: 0 PID: 2580 at fs/ext4/file.c:319
CPU: 0 PID: 2580 Comm: bb Not tainted 6.3.0-rc1-00004-g703695902cfa
RIP: 0010:ext4_file_write_iter+0xbc7/0xd10
Call Trace:
vfs_write+0x3b1/0x5c0
ksys_write+0x77/0x160
__x64_sys_write+0x22/0x30
do_syscall_64+0x39/0x80
Reproducer:
1. create corrupted image and mount it:
mke2fs -t ext4 /tmp/foo.img 200
debugfs -wR "sif size 25700" /tmp/foo.img
mount -t ext4 /tmp/foo.img /mnt
cd /mnt
echo 123 > file
2. Run the reproducer program:
posix_memalign(&buf, 1024, 1024)
fd = open("file", O_RDWR | O_DIRECT);
ioctl(fd, EXT4_IOC_SWAP_BOOT);
write(fd, buf, 1024);
Fix this by setting i_disksize as well as i_size to zero when
initiaizing the boot loader inode.
Affected
22 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.20-1 (bookworm) | linux 6.1.20-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < d6c1447e483c05dbcfb3ff77ac04237a82070b8c | d6c1447e483c05dbcfb3ff77ac04237a82070b8c |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < 59eee0cdf8c036f554add97a4da7c06d7a9ff34a | 59eee0cdf8c036f554add97a4da7c06d7a9ff34a |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < 0d8a6c9a6415999fee1259ccf1796480c026b7d6 | 0d8a6c9a6415999fee1259ccf1796480c026b7d6 |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < 3f00c476da8fe7c4c34ea16abb55d74127120413 | 3f00c476da8fe7c4c34ea16abb55d74127120413 |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < 01a821aacc64d4b05dafd239dbc9b7856686002f | 01a821aacc64d4b05dafd239dbc9b7856686002f |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < 9cb27b1e76f0cc886ac09055bc41c0ab3f205167 | 9cb27b1e76f0cc886ac09055bc41c0ab3f205167 |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < 9e9a4cc5486356158554f6ad73027d8635a48b34 | 9e9a4cc5486356158554f6ad73027d8635a48b34 |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < f5361da1e60d54ec81346aee8e3d8baf1be0b762 | f5361da1e60d54ec81346aee8e3d8baf1be0b762 |
| linux | linux_kernel | < 4.14.310 | 4.14.310 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 0 < 6.1.20-1 | 6.1.20-1 |
| linux | linux_kernel | >= 4.15 < 4.19.278 | 4.19.278 |
| linux | linux_kernel | >= 4.20 < 5.4.237 | 5.4.237 |
| linux | linux_kernel | >= 5.11 < 5.15.103 | 5.15.103 |
| linux | linux_kernel | >= 5.16 < 6.1.20 | 6.1.20 |
| linux | linux_kernel | >= 5.5 < 5.10.175 | 5.10.175 |
| linux | linux_kernel | >= 6.2 < 6.2.7 | 6.2.7 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: ext4: zero i_disksize when initializing the bootloader inode
vendor_redhat·2025-05-02·CVSS 5.5
CVE-2023-53101 [MEDIUM] kernel: ext4: zero i_disksize when initializing the bootloader inode
kernel: ext4: zero i_disksize when initializing the bootloader inode
In the Linux kernel, the following vulnerability has been resolved:
ext4: zero i_disksize when initializing the bootloader inode
If the boot loader inode has never been used before, the
EXT4_IOC_SWAP_BOOT inode will initialize it, including setting the
i_size to 0. However, if the "never before used" boot loader has a
non-zero i_size, then i_disksize will be non-zero, and the
inconsistency between i_size and i_disksize can trigger a kernel
warning:
WARNING: CPU: 0 PID: 2580 at fs/ext4/file.c:319
CPU: 0 PID: 2580 Comm: bb Not tainted 6.3.0-rc1-00004-g703695902cfa
RIP: 0010:ext4_file_write_iter+0xbc7/0xd10
Call Trace:
vfs_write+0x3b1/0x5c0
ksys_write+0x77/0x160
__x64_sys_write+0x22/0x30
do_syscall_64+0x39/0x80
Reproducer:
Debian
CVE-2023-53101: linux - In the Linux kernel, the following vulnerability has been resolved: ext4: zero ...
vendor_debian·2023·CVSS 5.5
CVE-2023-53101 [MEDIUM] CVE-2023-53101: linux - In the Linux kernel, the following vulnerability has been resolved: ext4: zero ...
In the Linux kernel, the following vulnerability has been resolved: ext4: zero i_disksize when initializing the bootloader inode If the boot loader inode has never been used before, the EXT4_IOC_SWAP_BOOT inode will initialize it, including setting the i_size to 0. However, if the "never before used" boot loader has a non-zero i_size, then i_disksize will be non-zero, and the inconsistency between i_size and i_disksize can trigger a kernel warning: WARNING: CPU: 0 PID: 2580 at fs/ext4/file.c:319 CPU: 0 PID: 2580 Comm: bb Not tainted 6.3.0-rc1-00004-g703695902cfa RIP: 0010:ext4_file_write_iter+0xbc7/0xd10 Call Trace: vfs_write+0x3b1/0x5c0 ksys_write+0x77/0x160 __x64_sys_write+0x22/0x30 do_syscall_64+0x39/0x80 Reproducer: 1. create corrupted image and mount it: mke2fs -t ext4 /tmp/foo.img 20
GHSA
GHSA-j8pm-fwxh-cj2q: In the Linux kernel, the following vulnerability has been resolved:
ext4: zero i_disksize when initializing the bootloader inode
If the boot loader
ghsa_unreviewed·2025-05-02
CVE-2023-53101 [MEDIUM] GHSA-j8pm-fwxh-cj2q: In the Linux kernel, the following vulnerability has been resolved:
ext4: zero i_disksize when initializing the bootloader inode
If the boot loader
In the Linux kernel, the following vulnerability has been resolved:
ext4: zero i_disksize when initializing the bootloader inode
If the boot loader inode has never been used before, the
EXT4_IOC_SWAP_BOOT inode will initialize it, including setting the
i_size to 0. However, if the "never before used" boot loader has a
non-zero i_size, then i_disksize will be non-zero, and the
inconsistency between i_size and i_disksize can trigger a kernel
warning:
WARNING: CPU: 0 PID: 2580 at fs/ext4/file.c:319
CPU: 0 PID: 2580 Comm: bb Not tainted 6.3.0-rc1-00004-g703695902cfa
RIP: 0010:ext4_file_write_iter+0xbc7/0xd10
Call Trace:
vfs_write+0x3b1/0x5c0
ksys_write+0x77/0x160
__x64_sys_write+0x22/0x30
do_syscall_64+0x39/0x80
Reproducer:
1. create corrupted image and mount it:
mke2fs -t ext4 /tmp/foo.im
OSV
CVE-2023-53101: In the Linux kernel, the following vulnerability has been resolved: ext4: zero i_disksize when initializing the bootloader inode If the boot loader in
osv·2025-05-02·CVSS 5.5
CVE-2023-53101 [MEDIUM] CVE-2023-53101: In the Linux kernel, the following vulnerability has been resolved: ext4: zero i_disksize when initializing the bootloader inode If the boot loader in
In the Linux kernel, the following vulnerability has been resolved: ext4: zero i_disksize when initializing the bootloader inode If the boot loader inode has never been used before, the EXT4_IOC_SWAP_BOOT inode will initialize it, including setting the i_size to 0. However, if the "never before used" boot loader has a non-zero i_size, then i_disksize will be non-zero, and the inconsistency between i_size and i_disksize can trigger a kernel warning: WARNING: CPU: 0 PID: 2580 at fs/ext4/file.c:319 CPU: 0 PID: 2580 Comm: bb Not tainted 6.3.0-rc1-00004-g703695902cfa RIP: 0010:ext4_file_write_iter+0xbc7/0xd10 Call Trace: vfs_write+0x3b1/0x5c0 ksys_write+0x77/0x160 __x64_sys_write+0x22/0x30 do_syscall_64+0x39/0x80 Reproducer: 1. create corrupted image and mount it: mke2fs -t ext4 /tmp/foo.img 20
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/01a821aacc64d4b05dafd239dbc9b7856686002fhttps://git.kernel.org/stable/c/0d8a6c9a6415999fee1259ccf1796480c026b7d6https://git.kernel.org/stable/c/3f00c476da8fe7c4c34ea16abb55d74127120413https://git.kernel.org/stable/c/59eee0cdf8c036f554add97a4da7c06d7a9ff34ahttps://git.kernel.org/stable/c/9cb27b1e76f0cc886ac09055bc41c0ab3f205167https://git.kernel.org/stable/c/9e9a4cc5486356158554f6ad73027d8635a48b34https://git.kernel.org/stable/c/d6c1447e483c05dbcfb3ff77ac04237a82070b8chttps://git.kernel.org/stable/c/f5361da1e60d54ec81346aee8e3d8baf1be0b762
2025-05-02
Published