CVE-2025-38650

hfsplus: remove mutex_lock check in hfsplus_free_extents

MEDIUM
5.5
CVSS Score
Published: August 22, 2025 at 04:00 PM UTC
Updated: June 17, 2026 at 09:17 AM UTC
2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.19 ≤ v < 5.10.2414.19 ≤ v < 5.15.1904.19 ≤ v < 5.4.2974.19 ≤ v < 6.1.1484.19 ≤ v < 6.12.424.19 ≤ v < 6.15.104.19 ≤ v < 6.16.14.19 ≤ v < 6.174.19 ≤ v < 6.6.1025.11 ≤ v < 5.15.1905.16 ≤ v < 6.1.1485.5 ≤ v < 5.10.2416.13 ≤ v < 6.15.106.16 ≤ v < 6.16.16.2 ≤ v < 6.6.1026.7 ≤ v < 6.12.4231651c607151f1034cfb57e5a78678bea54c362b4.19
Vendor states this is fixed in 0807e4ac59a546f2346961c5e26a98901594b205 (fixed)
Vendor states this is fixed in 084933961ecda7561dedfb78c4676ccb90c91ada (fixed)
Vendor states this is fixed in 14922f0cc92e010b160121679c0a6ca072f4e975 (fixed)
Vendor states this is fixed in 314310166ba1fdff7660dfd9d18ea42d7058f7ae (fixed)
Vendor states this is fixed in 5055b7db94110f228961dea6b74eed0a93a50b01 (fixed)
Vendor states this is fixed in 9764b8bb9f5f94df105cd2ac43829dd0d2c82b9f (fixed)
Vendor states this is fixed in a19ce9230b22a0866313932e7964cf05557a6008 (fixed)
Vendor states this is fixed in fcb96956c921f1aae7e7b477f2435c56f77a31b4 (fixed)
Vendor states this is fixed in fdd6aca652122d6e97787e88d7dd53ddc8b74e7e (fixed)
Vendor states this is fixed in 4.19 (unaffected)
Vendor states this is fixed in 5.10.241 (unaffected)
Vendor states this is fixed in 5.15.190 (unaffected)
Vendor states this is fixed in 5.4.297 (unaffected)
Vendor states this is fixed in 6.1.148 (unaffected)
Vendor states this is fixed in 6.12.42 (unaffected)
Vendor states this is fixed in 6.15.10 (unaffected)
Vendor states this is fixed in 6.16.1 (unaffected)
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.6.102 (unaffected)

References (11)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/0807e4ac59a546f2346961c5e26a98901594b205
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/084933961ecda7561dedfb78c4676ccb90c91ada
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/14922f0cc92e010b160121679c0a6ca072f4e975
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/314310166ba1fdff7660dfd9d18ea42d7058f7ae
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5055b7db94110f228961dea6b74eed0a93a50b01
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9764b8bb9f5f94df105cd2ac43829dd0d2c82b9f
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a19ce9230b22a0866313932e7964cf05557a6008
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/fcb96956c921f1aae7e7b477f2435c56f77a31b4

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card