Squashfs: check return result of sb_min_blocksize
In the Linux kernel, the following vulnerability has been resolved: Squashfs: check return result of sb_min_blocksize Syzkaller reports an "UBSAN: shift-out-of-bounds in squashfs_bio_read" bug. Syzkaller forks multiple processes which after mounting the Squashfs filesystem, issues an ioctl("/dev/loop0", LOOP_SET_BLOCK_SIZE, 0x8000). Now if this ioctl occurs at the same time another process is in the process of mounting a Squashfs filesystem on /dev/loop0, the failure occurs. When this happens the following code in squashfs_fill_super() fails. ---- msblk->devblksize = sb_min_blocksize(sb, SQUASHFS_DEVBLK_SIZE); msblk->devblksize_log2 = ffz(~msblk->devblksize); ---- sb_min_blocksize() returns 0, which means msblk->devblksize is set to 0. As a result, ffz(~msblk->devblksize) returns 64, and msblk->devblksize_log2 is set to 64. This subsequently causes the UBSAN: shift-out-of-bounds in fs/squashfs/block.c:195:36 shift exponent 64 is too large for 64-bit type 'u64' (aka 'unsigned long long') This commit adds a check for a 0 return by sb_min_blocksize().
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.239, 5.15.186, 5.4.295, 6.1.142, 6.12.34, 6.15.3, 6.6.94
- CVEs
- CVE-2025-38415
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 00:45 UTC · Revision 1
Source evidence
Squashfs: check return result of sb_min_blocksize
core-osv · Original sourcePublished 25 Jul 2025, 13:32 UTC
In the Linux kernel, the following vulnerability has been resolved: Squashfs: check return result of sb_min_blocksize Syzkaller reports an "UBSAN: shift-out-of-bounds in squashfs_bio_read" bug. Syzkaller forks multiple processes which after mounting the Squashfs filesystem, issues an ioctl("/dev/loop0", LOOP_SET_BLOCK_SIZE, 0x8000). Now if this ioctl occurs at the same time another process is in the process of mounting a Squashfs filesystem on /dev/loop0, the failure occurs. When this happens the following code in squashfs_fill_super() fails. ---- msblk->devblksize = sb_min_blocksize(sb, SQUASHFS_DEVBLK_SIZE); msblk->devblksize_log2 = ffz(~msblk->devblksize); ---- sb_min_blocksize() returns 0, which means msblk->devblksize is set to 0. As a result, ffz(~msblk->devblksize) returns 64, and msblk->devblksize_log2 is set to 64. This subsequently causes the UBSAN: shift-out-of-bounds in fs/squashfs/block.c:195:36 shift exponent 64 is too large for 64-bit type 'u64' (aka 'unsigned long long') This commit adds a check for a 0 return by sb_min_blocksize().
osv:CVE-2025-38415
Kernel
Fixed versions: 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.94, 6.12.34, 6.15.3
Complete source record
{
"id": "f39db0c5776ccc83cb312f883a6bddc59a1f0aa7e162e2b5b7f36ea83f1e356b",
"url": "https://osv.dev/vulnerability/CVE-2025-38415",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Squashfs: check return result of sb_min_blocksize",
"summary": "In the Linux kernel, the following vulnerability has been resolved: Squashfs: check return result of sb_min_blocksize Syzkaller reports an \"UBSAN: shift-out-of-bounds in squashfs_bio_read\" bug. Syzkaller forks multiple processes which after mounting the Squashfs filesystem, issues an ioctl(\"/dev/loop0\", LOOP_SET_BLOCK_SIZE, 0x8000). Now if this ioctl occurs at the same time another process is in the process of mounting a Squashfs filesystem on /dev/loop0, the failure occurs. When this happens the following code in squashfs_fill_super() fails. ---- msblk->devblksize = sb_min_blocksize(sb, SQUASHFS_DEVBLK_SIZE); msblk->devblksize_log2 = ffz(~msblk->devblksize); ---- sb_min_blocksize() returns 0, which means msblk->devblksize is set to 0. As a result, ffz(~msblk->devblksize) returns 64, and msblk->devblksize_log2 is set to 64. This subsequently causes the UBSAN: shift-out-of-bounds in fs/squashfs/block.c:195:36 shift exponent 64 is too large for 64-bit type 'u64' (aka 'unsigned long long') This commit adds a check for a 0 return by sb_min_blocksize().",
"evidence": "osv:CVE-2025-38415",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.4.295",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.239",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.186",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.142",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.94",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.34",
"evidence": "/affected/1/ranges"
},
{
"value": "6.15.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-38415",
"aliases": [
"CVE-2025-38415"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "0aa666190509ffab81c202c5095a166be23961ac"
},
{
"fixed": "db7096ea160e40d78c67fce52e7cc51bde049497"
},
{
"fixed": "549f9e3d7b60d53808c98b9fde49b4f46d0524a5"
},
{
"fixed": "5c51aa862cbeed2f3887f0382a2708956710bd68"
},
{
"fixed": "6abf6b78c6fb112eee495f5636ffcc350dd2ce25"
},
{
"fixed": "4f99357dadbf9c979ad737156ad4c37fadf7c56b"
},
{
"fixed": "0aff95d9bc7fb5400ca8af507429c4b067bdb425"
},
{
"fixed": "295ab18c2dbce8d0ac6ecf7c5187e16e1ac8b282"
},
{
"fixed": "734aa85390ea693bb7eaf2240623d41b03705c84"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38415.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "2.6.29"
},
{
"fixed": "5.4.295"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.239"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.186"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.142"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.94"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.34"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.15.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38415.json"
}
}
],
"modified": "2026-10-28T02:30:52.340842773Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0aff95d9bc7fb5400ca8af507429c4b067bdb425",
"https://git.kernel.org/stable/c/295ab18c2dbce8d0ac6ecf7c5187e16e1ac8b282",
"https://git.kernel.org/stable/c/4f99357dadbf9c979ad737156ad4c37fadf7c56b",
"https://git.kernel.org/stable/c/549f9e3d7b60d53808c98b9fde49b4f46d0524a5",
"https://git.kernel.org/stable/c/5c51aa862cbeed2f3887f0382a2708956710bd68",
"https://git.kernel.org/stable/c/6abf6b78c6fb112eee495f5636ffcc350dd2ce25",
"https://git.kernel.org/stable/c/734aa85390ea693bb7eaf2240623d41b03705c84",
"https://git.kernel.org/stable/c/db7096ea160e40d78c67fce52e7cc51bde049497",
"https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html",
"https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38415.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-38415",
"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/2025/38xxx/CVE-2025-38415.json"
}
},
"related_cves": [
{
"value": "CVE-2025-38415",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 521072,
"published_at": "2025-07-25T13:32:09.711+00:00"
}