CVE-2025-23150 — linux / linux_kernel
Off-by-one ErrorIn the Linux kernel, the following vulnerability has been resolved:
ext4: fix off-by-one error in do_split
Syzkaller detected a use-after-free issue in ext4_insert_dentry that was caused by out-of-bounds access due to incorrect splitting in do_split.
BUG: KASAN: use-after-free in ext4_insert_dentry+0x36a/0x6d0 fs/ext4/namei.c:2109 Write of size 251 at addr ffff888074572f14 by task syz-executor335/5847
CPU: 0 UID: 0 PID: 5847 Comm: syz-executor335 Not tainted 6.12.0-rc6-syzkaller-00318-ga9cda7c0ffed #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 kasan_check_range+0x282/0x290 mm/kasan/generic.c:189 __asan_memcpy+0x40/0x70 mm/kasan/shadow.c:106 ext4_insert_dentry+0x36a/0x6d0 fs/ext4/namei.c:2109 add_dirent_to_buf+0x3d9/0x750 fs/ext4/namei.c:2154 make_indexed_dir+0xf98/0x1600 fs/ext4/namei.c:2351 ext4_add_entry+0x222a/0x25d0 fs/ext4/namei.c:2455 ext4_add_nondir+0x8d/0x290 fs/ext4/namei.c:2796 ext4_symlink+0x920/0xb50 fs/ext4/namei.c:3431 vfs_symlink+0x137/0x2e0 fs/namei.c:4615 do_symlinkat+0x222/0x3a0 fs/namei.c:4641 __do_sys_symlink fs/namei.c:4662 [inline] __se_sys_symlink fs/namei.c:4660 [inline] __x64_sys_symlink+0x7a/0x90 fs/namei.c:4660 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f </TASK>
The following loop is located right above 'if' statement.
for (i = count-1; i >= 0; i--) { /* is more than half of this entry in 2nd half of the block? */ if (size + map[i].size/2 > blocksize/2) break; size += map[i].size; move++; }
'i' in this case could go down to -1, in which case sum of active entries wouldn't exceed half the block size, but previous behaviour would also do split in half if sum would exceed at the very last block, which in case of having too many long name files in a single block could lead to out-of-bounds access and following use-after-free.
Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
| Software | From | Fixed in |
|---|---|---|
| linux / linux_kernel | 4.4.234 | 4.5 |
| linux / linux_kernel | 4.9.234 | 4.10 |
| linux / linux_kernel | 4.14.195 | 4.15 |
| linux / linux_kernel | 4.19.142 | 4.20 |
| linux / linux_kernel | 5.4.61 | 5.4.293 |
| linux / linux_kernel | 5.7.18 | 5.8 |
| linux / linux_kernel | 5.8.4 | 5.9 |
| linux / linux_kernel | 5.9.1 | 5.10.237 |
| linux / linux_kernel | 5.11 | 5.15.181 |
| linux / linux_kernel | 5.16 | 6.1.135 |
| linux / linux_kernel | 6.2 | 6.6.88 |
| linux / linux_kernel | 6.7 | 6.12.24 |
| linux / linux_kernel | 6.13 | 6.13.12 |
| linux / linux_kernel | 6.14 | 6.14.3 |
| linux / linux_kernel | 5.9 | 5.9.x |
| linux / linux_kernel | 5.9-rc2 | 5.9-rc2.x |
| linux / linux_kernel | 5.9-rc3 | 5.9-rc3.x |
| linux / linux_kernel | 5.9-rc4 | 5.9-rc4.x |
| linux / linux_kernel | 5.9-rc5 | 5.9-rc5.x |
| linux / linux_kernel | 5.9-rc6 | 5.9-rc6.x |
| linux / linux_kernel | 5.9-rc7 | 5.9-rc7.x |
| linux / linux_kernel | 5.9-rc8 | 5.9-rc8.x |
| linux / linux_kernel | 6.15-rc1 | 6.15-rc1.x |
| debian / debian_linux | 11.0 | 11.0.x |
- https://git.kernel.org/stable/c/16d9067f00e3a7d1df7c3aa9c20d214923d27e10
- https://git.kernel.org/stable/c/17df39f455f1289319d4d09e4826aa46852ffd17
- https://git.kernel.org/stable/c/2883e9e74f73f9265e5f8d1aaaa89034b308e433
- https://git.kernel.org/stable/c/2eeb1085bf7bd5c7ba796ca4119925fa5d336a3f
- https://git.kernel.org/stable/c/35d0aa6db9d93307085871ceab8a729594a98162
- https://git.kernel.org/stable/c/515c34cff899eb5dae6aa7eee01c1295b07d81af
- https://git.kernel.org/stable/c/94824ac9a8aaf2fb3c54b4bdde842db80ffa555d
- https://git.kernel.org/stable/c/ab0cc5c25552ae0d20eae94b40a93be11b080fc5
- https://git.kernel.org/stable/c/b96bd2c3db26ad0daec5b78c85c098b53900e2e1
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Deep Security Visibility Without the Complexity
SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.
- No setup fees
- 5-min deployment
- Cancel anytime
Frequently Asked Questions
A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.
CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.
A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.
Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.
Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.
SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.