OESA-2025-2661 (CVE-2025-38415)
Vulnerability from osv_openeuler – Published: 2025-11-14 11:09 – Updated: 2026-08-06 11:09 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
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().(CVE-2025-38415)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"bpftool-debuginfo-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"kernel-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"kernel-debuginfo-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"kernel-debugsource-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"kernel-devel-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"kernel-headers-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"kernel-source-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"kernel-tools-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"kernel-tools-debuginfo-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"kernel-tools-devel-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"perf-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"perf-debuginfo-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"python3-perf-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm",
"python3-perf-debuginfo-5.10.0-289.0.0.192.oe2203sp4.aarch64.rpm"
],
"src": [
"kernel-5.10.0-289.0.0.192.oe2203sp4.src.rpm"
],
"x86_64": [
"bpftool-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"bpftool-debuginfo-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"kernel-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"kernel-debuginfo-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"kernel-debugsource-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"kernel-devel-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"kernel-headers-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"kernel-source-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"kernel-tools-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"kernel-tools-debuginfo-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"kernel-tools-devel-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"perf-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"perf-debuginfo-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"python3-perf-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm",
"python3-perf-debuginfo-5.10.0-289.0.0.192.oe2203sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP4",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-22.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.10.0-289.0.0.192.oe2203sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Low"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSquashfs: check return result of sb_min_blocksize\n\nSyzkaller reports an \u0026quot;UBSAN: shift-out-of-bounds in squashfs_bio_read\u0026quot; bug.\n\nSyzkaller forks multiple processes which after mounting the Squashfs\nfilesystem, issues an ioctl(\u0026quot;/dev/loop0\u0026quot;, LOOP_SET_BLOCK_SIZE, 0x8000). \nNow if this ioctl occurs at the same time another process is in the\nprocess of mounting a Squashfs filesystem on /dev/loop0, the failure\noccurs. When this happens the following code in squashfs_fill_super()\nfails.\n\n----\nmsblk-\u0026gt;devblksize = sb_min_blocksize(sb, SQUASHFS_DEVBLK_SIZE);\nmsblk-\u0026gt;devblksize_log2 = ffz(~msblk-\u0026gt;devblksize);\n----\n\nsb_min_blocksize() returns 0, which means msblk-\u0026gt;devblksize is set to 0.\n\nAs a result, ffz(~msblk-\u0026gt;devblksize) returns 64, and msblk-\u0026gt;devblksize_log2\nis set to 64.\n\nThis subsequently causes the\n\nUBSAN: shift-out-of-bounds in fs/squashfs/block.c:195:36\nshift exponent 64 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka\n\u0026apos;unsigned long long\u0026apos;)\n\nThis commit adds a check for a 0 return by sb_min_blocksize().(CVE-2025-38415)",
"id": "OESA-2025-2661",
"modified": "2026-08-06T11:09:47Z",
"published": "2025-11-14T11:09:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2661"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38415"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2025-38415"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.