CVE-2025-38650 json
hfsplus: remove mutex_lock check in hfsplus_free_extents
published 2025-08-22 14 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-25552
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.4.297, 5.10.241, 5.15.190, 6.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1, 6.17
- linux Debian 12 6.1.148-1
- linux Debian 13 6.12.43-1
- linux Debian 14 6.16.3-1
debian advisories DEBIAN-CVE-2025-38650
- linux Ubuntu 22.04 LTS 5.15.0-163.173
- linux Ubuntu 24.04 LTS 6.8.0-100.100
- linux-aws Ubuntu 22.04 LTS 5.15.0-1097.104
- linux-aws Ubuntu 24.04 LTS 6.8.0-1046.49
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1097.106
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1047.50
- linux-gke Ubuntu 22.04 LTS 5.15.0-1093.99
- linux-gke Ubuntu 24.04 LTS 6.8.0-1043.48
ubuntu advisories UBUNTU-CVE-2025-38650
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-azure SLE Module for Public Cloud 15 SP6, openSUSE Leap 15.6 6.4.0-150600.8.52.1
- kernel-syms-azure SLE Module for Public Cloud 15 SP6, openSUSE Leap 15.6 6.4.0-150600.8.52.1
- kernel-source-azure SLE Module for Public Cloud 15 SP6, openSUSE Leap 15.6 6.4.0-150600.8.52.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.20.15.2
- kernel-syms-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.20.15.1
- kernel-source-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.20.15.2
- kernel-coco SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.32.coco15sp6.1
- kernel-syms-coco SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.32.coco15sp6.1
suse advisories SUSE-SU-2025:03634-1SUSE-SU-2025:03633-1SUSE-SU-2025:03602-1SUSE-SU-2025:03382-1SUSE-SU-2025:20739-1SUSE-SU-2025:20756-1
- git.kernel.org/stable/c/0807e4ac59a546f2346961c5e26a98901594b205 commit
- git.kernel.org/stable/c/fdd6aca652122d6e97787e88d7dd53ddc8b74e7e commit
- git.kernel.org/stable/c/14922f0cc92e010b160121679c0a6ca072f4e975 commit
- git.kernel.org/stable/c/a19ce9230b22a0866313932e7964cf05557a6008 commit
- git.kernel.org/stable/c/084933961ecda7561dedfb78c4676ccb90c91ada commit
- git.kernel.org/stable/c/5055b7db94110f228961dea6b74eed0a93a50b01 commit
- git.kernel.org/stable/c/9764b8bb9f5f94df105cd2ac43829dd0d2c82b9f commit
- git.kernel.org/stable/c/314310166ba1fdff7660dfd9d18ea42d7058f7ae commit
- git.kernel.org/stable/c/fcb96956c921f1aae7e7b477f2435c56f77a31b4 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-38650 updated cvss 2.5
kernel: hfsplus: remove mutex_lock check in hfsplus_free_extents
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-667 Improper Locking
- Technology feeds
References
-
git.kernel.org
/stable/c/0807e4ac59a546f2346961c5e26a98901594b205
patch
-
git.kernel.org
/stable/c/fdd6aca652122d6e97787e88d7dd53ddc8b74e7e
patch
-
git.kernel.org
/stable/c/14922f0cc92e010b160121679c0a6ca072f4e975
patch
-
git.kernel.org
/stable/c/a19ce9230b22a0866313932e7964cf05557a6008
patch
-
git.kernel.org
/stable/c/084933961ecda7561dedfb78c4676ccb90c91ada
patch
-
git.kernel.org
/stable/c/5055b7db94110f228961dea6b74eed0a93a50b01
patch
-
git.kernel.org
/stable/c/9764b8bb9f5f94df105cd2ac43829dd0d2c82b9f
patch
-
git.kernel.org
/stable/c/314310166ba1fdff7660dfd9d18ea42d7058f7ae
patch
-
git.kernel.org
/stable/c/fcb96956c921f1aae7e7b477f2435c56f77a31b4
patch
-
lists.debian.org
/debian-lts-announce/2025/10/msg00008.html
third-party-advisory
-
lists.debian.org
/debian-lts-announce/2025/10/msg00007.html
third-party-advisory
Sources
- CVE List CVE-2025-38650
- NVD CVE-2025-38650
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.