CVE-2025-38650: hfsplus: remove mutex_lock check in hfsplus_free_extents
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0807e4ac59a546f2346961c5e26a98901594b205, 084933961ecda7561dedfb78c4676ccb90c91ada, 14922f0cc92e010b160121679c0a6ca072f4e975; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1.
Low priority for now. Upgrade to Linux Linux 0807e4ac59a546f2346961c5e26a98901594b205, 084933961ecda7561dedfb78c4676ccb90c91ada, 14922f0cc92e010b160121679c0a6ca072f4e975; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 22, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-667
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.5 and later · before 5.10.241
- linux linux kernel5.11 and later · before 5.15.190
- linux linux kernel5.16 and later · before 6.1.148
- linux linux kernel4.19 and later · before 5.4.297
- linux linux kernel6.7 and later · before 6.12.42
- linux linux kernel6.13 and later · before 6.15.10
- linux linux kernel6.16 and later · before 6.16.1
- linux linux kernel6.2 and later · before 6.6.102
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.19affected
- 31651c607151f1034cfb57e5a78678bea54c362b and later · before 0807e4ac59a546f2346961c5e26a98901594b205affected · git
- 31651c607151f1034cfb57e5a78678bea54c362b and later · before fdd6aca652122d6e97787e88d7dd53ddc8b74e7eaffected · git
- 31651c607151f1034cfb57e5a78678bea54c362b and later · before 14922f0cc92e010b160121679c0a6ca072f4e975affected · git
- 31651c607151f1034cfb57e5a78678bea54c362b and later · before a19ce9230b22a0866313932e7964cf05557a6008affected · git
- 31651c607151f1034cfb57e5a78678bea54c362b and later · before 084933961ecda7561dedfb78c4676ccb90c91adaaffected · git
- 31651c607151f1034cfb57e5a78678bea54c362b and later · before 5055b7db94110f228961dea6b74eed0a93a50b01affected · git
- 31651c607151f1034cfb57e5a78678bea54c362b and later · before 9764b8bb9f5f94df105cd2ac43829dd0d2c82b9faffected · git
- 31651c607151f1034cfb57e5a78678bea54c362b and later · before 314310166ba1fdff7660dfd9d18ea42d7058f7aeaffected · git
- 31651c607151f1034cfb57e5a78678bea54c362b and later · before fcb96956c921f1aae7e7b477f2435c56f77a31b4affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.148-1 | 6.1.148-1 |
| Debian:13 | linux | before 6.12.43-1 | 6.12.43-1 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38648Aug 22, 2025 · spi: stm32: Check for cfg availability in stm32_spi_probe22Monitor
- ← EarlierCVE-2025-38649Aug 22, 2025 · arm64: dts: qcom: qcs615: fix a crash issue caused by infinite loop for Coresight22Monitor
- Later →CVE-2025-38651Aug 22, 2025 · landlock: Fix warning from KUnit tests22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0807e4ac59a546f2346961c5e26a98901594b205 | Vendor (CNA) |
| Linux Linux | 084933961ecda7561dedfb78c4676ccb90c91ada | Vendor (CNA) |
| Linux Linux | 14922f0cc92e010b160121679c0a6ca072f4e975 | Vendor (CNA) |
| Linux Linux | 314310166ba1fdff7660dfd9d18ea42d7058f7ae | Vendor (CNA) |
| Linux Linux | 5055b7db94110f228961dea6b74eed0a93a50b01 | Vendor (CNA) |
| Linux Linux | 9764b8bb9f5f94df105cd2ac43829dd0d2c82b9f | Vendor (CNA) |
| Linux Linux | a19ce9230b22a0866313932e7964cf05557a6008 | Vendor (CNA) |
| Linux Linux | fcb96956c921f1aae7e7b477f2435c56f77a31b4 | Vendor (CNA) |
| Linux Linux | fdd6aca652122d6e97787e88d7dd53ddc8b74e7e | Vendor (CNA) |
| azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 | 6.6.104.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.148-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- git.kernel.org/stable/c/084933961ecda7561dedfb78c4676ccb90c91ada
- git.kernel.org/stable/c/14922f0cc92e010b160121679c0a6ca072f4e975
- git.kernel.org/stable/c/314310166ba1fdff7660dfd9d18ea42d7058f7ae
- git.kernel.org/stable/c/5055b7db94110f228961dea6b74eed0a93a50b01
- git.kernel.org/stable/c/9764b8bb9f5f94df105cd2ac43829dd0d2c82b9f
- git.kernel.org/stable/c/a19ce9230b22a0866313932e7964cf05557a6008
- git.kernel.org/stable/c/fcb96956c921f1aae7e7b477f2435c56f77a31b4
- git.kernel.org/stable/c/fdd6aca652122d6e97787e88d7dd53ddc8b74e7e
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.