CVE-2025-38650

In the Linux kernel, the following vulnerability has been resolved: hfsplus: remove mutex_lock check in hfsplus_free_extents Syzbot reported an issue in hfsplus filesystem: ------------[ cut here ]------------ WARNING: CPU: 0 PID: 4400 at fs/hfsplus/extents.c:346 hfsplus_free_extents+0x700/0xad0 Call Trace: <TASK> hfsplus_file_truncate+0x768/0xbb0 fs/hfsplus/extents.c:606 hfsplus_write_begin+0xc2/0xd0 fs/hfsplus/inode.c:56 cont_expand_zero fs/buffer.c:2383 [inline] cont_write_begin+0x2cf/0x860 fs/buffer.c:2446 hfsplus_write_begin+0x86/0xd0 fs/hfsplus/inode.c:52 generic_cont_expand_simple+0x151/0x250 fs/buffer.c:2347 hfsplus_setattr+0x168/0x280 fs/hfsplus/inode.c:263 notify_change+0xe38/0x10f0 fs/attr.c:420 do_truncate+0x1fb/0x2e0 fs/open.c:65 do_sys_ftruncate+0x2eb/0x380 fs/open.c:193 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd To avoid deadlock, Commit 31651c607151 ("hfsplus: avoid deadlock on file truncation") unlock extree before hfsplus_free_extents(), and add check wheather extree is locked in hfsplus_free_extents(). However, when operations such as hfsplus_file_release, hfsplus_setattr, hfsplus_unlink, and hfsplus_get_block are executed concurrently in different files, it is very likely to trigger the WARN_ON, which will lead syzbot and xfstest to consider it as an abnormality. The comment above this warning also describes one of the easy triggering situations, which can easily trigger and cause xfstest&syzbot to report errors. [task A] [task B] ->hfsplus_file_release ->hfsplus_file_truncate ->hfs_find_init ->mutex_lock ->mutex_unlock ->hfsplus_write_begin ->hfsplus_get_block ->hfsplus_file_extend ->hfsplus_ext_read_extent ->hfs_find_init ->mutex_lock ->hfsplus_free_extents WARN_ON(mutex_is_locked) !!! Several threads could try to lock the shared extents tree. And warning can be triggered in one thread when another thread has locked the tree. This is the wrong behavior of the code and we need to remove the warning.
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

Configuration 2 (hide)

cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

History

07 Jan 2026, 17:36

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/0807e4ac59a546f2346961c5e26a98901594b205 - () https://git.kernel.org/stable/c/0807e4ac59a546f2346961c5e26a98901594b205 - Patch
References () https://git.kernel.org/stable/c/084933961ecda7561dedfb78c4676ccb90c91ada - () https://git.kernel.org/stable/c/084933961ecda7561dedfb78c4676ccb90c91ada - Patch
References () https://git.kernel.org/stable/c/14922f0cc92e010b160121679c0a6ca072f4e975 - () https://git.kernel.org/stable/c/14922f0cc92e010b160121679c0a6ca072f4e975 - Patch
References () https://git.kernel.org/stable/c/314310166ba1fdff7660dfd9d18ea42d7058f7ae - () https://git.kernel.org/stable/c/314310166ba1fdff7660dfd9d18ea42d7058f7ae - Patch
References () https://git.kernel.org/stable/c/5055b7db94110f228961dea6b74eed0a93a50b01 - () https://git.kernel.org/stable/c/5055b7db94110f228961dea6b74eed0a93a50b01 - Patch
References () https://git.kernel.org/stable/c/9764b8bb9f5f94df105cd2ac43829dd0d2c82b9f - () https://git.kernel.org/stable/c/9764b8bb9f5f94df105cd2ac43829dd0d2c82b9f - Patch
References () https://git.kernel.org/stable/c/a19ce9230b22a0866313932e7964cf05557a6008 - () https://git.kernel.org/stable/c/a19ce9230b22a0866313932e7964cf05557a6008 - Patch
References () https://git.kernel.org/stable/c/fcb96956c921f1aae7e7b477f2435c56f77a31b4 - () https://git.kernel.org/stable/c/fcb96956c921f1aae7e7b477f2435c56f77a31b4 - Patch
References () https://git.kernel.org/stable/c/fdd6aca652122d6e97787e88d7dd53ddc8b74e7e - () https://git.kernel.org/stable/c/fdd6aca652122d6e97787e88d7dd53ddc8b74e7e - Patch
References () https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html - () https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html - Third Party Advisory
References () https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html - () https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html - Third Party Advisory
First Time Linux
Debian
Debian debian Linux
Linux linux Kernel
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 5.5
CPE cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
CWE CWE-667

03 Nov 2025, 18:16

Type Values Removed Values Added
References
  • () https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html -
  • () https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html -

28 Aug 2025, 15:15

Type Values Removed Values Added
References
  • () https://git.kernel.org/stable/c/0807e4ac59a546f2346961c5e26a98901594b205 -
  • () https://git.kernel.org/stable/c/14922f0cc92e010b160121679c0a6ca072f4e975 -
  • () https://git.kernel.org/stable/c/fdd6aca652122d6e97787e88d7dd53ddc8b74e7e -
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: hfsplus: eliminar comprobación mutex_lock en hfsplus_free_extents Syzbot informó de un problema en el sistema de archivos hfsplus: ------------[ cortar aquí ]------------ ADVERTENCIA: CPU: 0 PID: 4400 en fs/hfsplus/extents.c:346 hfsplus_free_extents+0x700/0xad0 Rastreo de llamadas: hfsplus_file_truncate+0x768/0xbb0 fs/hfsplus/extents.c:606 hfsplus_write_begin+0xc2/0xd0 fs/hfsplus/inode.c:56 cont_expand_zero fs/buffer.c:2383 [en línea] cont_write_begin+0x2cf/0x860 fs/buffer.c:2446 hfsplus_write_begin+0x86/0xd0 fs/hfsplus/inode.c:52 generic_cont_expand_simple+0x151/0x250 fs/buffer.c:2347 hfsplus_setattr+0x168/0x280 fs/hfsplus/inode.c:263 notify_change+0xe38/0x10f0 fs/attr.c:420 do_truncate+0x1fb/0x2e0 fs/open.c:65 do_sys_ftruncate+0x2eb/0x380 fs/open.c:193 do_syscall_x64 arch/x86/entry/common.c:50 [en línea] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd Para evitar un bloqueo, el commit 31651c607151 ("hfsplus: evitar bloqueo al truncamiento de archivos") desbloquea el árbol externo antes de hfsplus_free_extents() y añade una comprobación de si el árbol externo está bloqueado en hfsplus_free_extents(). Sin embargo, cuando operaciones como hfsplus_file_release, hfsplus_setattr, hfsplus_unlink y hfsplus_get_block se ejecutan simultáneamente en archivos diferentes, es muy probable que se active WARN_ON, lo que hará que syzbot y xfstest lo consideren una anomalía. El comentario sobre esta advertencia también describe una de las situaciones de fácil activación, que puede fácilmente provocar que xfstest y syzbot reporten errores. [Tarea A] [Tarea B] -&gt;hfsplus_file_release -&gt;hfsplus_file_truncate -&gt;hfs_find_init -&gt;mutex_lock -&gt;mutex_unlock -&gt;hfsplus_write_begin -&gt;hfsplus_get_block -&gt;hfsplus_file_extend -&gt;hfsplus_ext_read_extent -&gt;hfs_find_init -&gt;mutex_lock -&gt;hfsplus_free_extents WARN_ON(mutex_is_locked) !!! Varios subprocesos podrían intentar bloquear el árbol de extensiones compartidas. Una advertencia puede activarse en un subproceso cuando otro subproceso ha bloqueado el árbol. Este comportamiento del código es incorrecto y debemos eliminar la advertencia.

22 Aug 2025, 16:15

Type Values Removed Values Added
New CVE

Information

Published : 2025-08-22 16:15

Updated : 2026-01-07 17:36


NVD link : CVE-2025-38650

Mitre link : CVE-2025-38650

CVE.ORG link : CVE-2025-38650


JSON object : View

Products Affected

debian

  • debian_linux

linux

  • linux_kernel
CWE
CWE-667

Improper Locking