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: 1. create corrupted image and mount it: mke2fs -t ext4 /tmp/foo.img 200 debugfs -wR "sif <5> 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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.14.310, 4.19.278, 5.10.175, 5.15.103, 5.4.237, 6.1.20, 6.2.7
- CVEs
- CVE-2023-53101
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 05:30 UTC · Revision 1
Source evidence
ext4: zero i_disksize when initializing the bootloader inode
core-osv · Original sourcePublished 2 May 2025, 15:55 UTC
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 <5> 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.
osv:CVE-2023-53101
Kernel
Fixed versions: 4.14.310, 4.19.278, 5.4.237, 5.10.175, 5.15.103, 6.1.20, 6.2.7
Complete source record
{
"id": "8f15930637bd74507af3bffb3f9778f3fa74e91966f28e2050ed78283f35e34a",
"url": "https://osv.dev/vulnerability/CVE-2023-53101",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "ext4: zero i_disksize when initializing the bootloader inode",
"summary": "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 <5> 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.",
"evidence": "osv:CVE-2023-53101",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.14.310",
"evidence": "/affected/1/ranges"
},
{
"value": "4.19.278",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.237",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.175",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.103",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.20",
"evidence": "/affected/1/ranges"
},
{
"value": "6.2.7",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2023-53101",
"aliases": [
"CVE-2023-53101"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "393d1d1d76933886d5e1ce603214c9987589c6d5"
},
{
"fixed": "d6c1447e483c05dbcfb3ff77ac04237a82070b8c"
},
{
"fixed": "59eee0cdf8c036f554add97a4da7c06d7a9ff34a"
},
{
"fixed": "0d8a6c9a6415999fee1259ccf1796480c026b7d6"
},
{
"fixed": "3f00c476da8fe7c4c34ea16abb55d74127120413"
},
{
"fixed": "01a821aacc64d4b05dafd239dbc9b7856686002f"
},
{
"fixed": "9cb27b1e76f0cc886ac09055bc41c0ab3f205167"
},
{
"fixed": "9e9a4cc5486356158554f6ad73027d8635a48b34"
},
{
"fixed": "f5361da1e60d54ec81346aee8e3d8baf1be0b762"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53101.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.10.0"
},
{
"fixed": "4.14.310"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.15.0"
},
{
"fixed": "4.19.278"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.237"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.175"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.103"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.20"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.2.7"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53101.json"
}
}
],
"modified": "2026-10-28T02:30:26.143040928Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/01a821aacc64d4b05dafd239dbc9b7856686002f",
"https://git.kernel.org/stable/c/0d8a6c9a6415999fee1259ccf1796480c026b7d6",
"https://git.kernel.org/stable/c/3f00c476da8fe7c4c34ea16abb55d74127120413",
"https://git.kernel.org/stable/c/59eee0cdf8c036f554add97a4da7c06d7a9ff34a",
"https://git.kernel.org/stable/c/9cb27b1e76f0cc886ac09055bc41c0ab3f205167",
"https://git.kernel.org/stable/c/9e9a4cc5486356158554f6ad73027d8635a48b34",
"https://git.kernel.org/stable/c/d6c1447e483c05dbcfb3ff77ac04237a82070b8c",
"https://git.kernel.org/stable/c/f5361da1e60d54ec81346aee8e3d8baf1be0b762",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53101.json",
"https://nvd.nist.gov/vuln/detail/CVE-2023-53101",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53101.json"
}
},
"related_cves": [
{
"value": "CVE-2023-53101",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 492731,
"published_at": "2025-05-02T15:55:43.804+00:00"
}