Linux Kernel up to 6.16.1 hfs hfs_bnode_read out-of-bounds

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Linux Kernel up to 6.16.1. This impacts the function hfs_bnode_read of the component hfs. This manipulation causes out-of-bounds.
This vulnerability appears as CVE-2025-38715. There is no available exploit.
It is recommended to upgrade the affected component.
Details
A vulnerability has been found in Linux Kernel up to 6.16.1 and classified as problematic. Affected by this vulnerability is the function hfs_bnode_read of the component hfs. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: hfs: fix slab-out-of-bounds in hfs_bnode_read() This patch introduces is_bnode_offset_valid() method that checks the requested offset value. Also, it introduces check_and_correct_requested_length() method that checks and correct the requested length (if it is necessary). These methods are used in hfs_bnode_read(), hfs_bnode_write(), hfs_bnode_clear(), hfs_bnode_copy(), and hfs_bnode_move() with the goal to prevent the access out of allocated memory and triggering the crash.
The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2025-38715 since 04/16/2025. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 261565 (Linux Distros Unpatched Vulnerability : CVE-2025-38715), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.4.297, 5.10.241, 5.15.190, 6.1.149, 6.6.103, 6.12.43, 6.15.11, 6.16.2 or 6.17-rc1 eliminates this vulnerability. Applying the patch e7d2dc2421e821e4045775e6dc226378328de6f6/67ecc81f6492275c9c54280532f558483c99c90e/a1a60e79502279f996e55052f50cc14919020475/fe2891a9c43ab87d1a210d61e6438ca6936e2f62/384a66b89f9540a9a8cb0f48807697dfabaece4c/efc095b35b23297e419c2ab4fc1ed1a8f0781a29/fc7f732984ec91f30be3e574e0644066d07f2b78/eec522fd0d28106b14a59ab2d658605febe4a3bb/a431930c9bac518bf99d6b1da526a7f37ddee8d8 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (261565) and CERT Bund (WID-SEC-2025-1976). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Debian Linux
- Amazon Linux 2
- Open Source Linux Kernel
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- RESF Rocky Linux
- Microsoft Azure
- Dell Secure Connect Gateway
- IBM QRadar SIEM
- IBM Security Verify Access
- Dell NetWorker
Product
Type
Vendor
Name
Version
- 5.4.296
- 5.10.240
- 5.15.189
- 6.1.148
- 6.6.102
- 6.12.0
- 6.12.1
- 6.12.2
- 6.12.3
- 6.12.4
- 6.12.5
- 6.12.6
- 6.12.7
- 6.12.8
- 6.12.9
- 6.12.10
- 6.12.11
- 6.12.12
- 6.12.13
- 6.12.14
- 6.12.15
- 6.12.16
- 6.12.17
- 6.12.18
- 6.12.19
- 6.12.20
- 6.12.21
- 6.12.22
- 6.12.23
- 6.12.24
- 6.12.25
- 6.12.26
- 6.12.27
- 6.12.28
- 6.12.29
- 6.12.30
- 6.12.31
- 6.12.32
- 6.12.33
- 6.12.34
- 6.12.35
- 6.12.36
- 6.12.37
- 6.12.38
- 6.12.39
- 6.12.40
- 6.12.41
- 6.12.42
- 6.15.0
- 6.15.1
- 6.15.2
- 6.15.3
- 6.15.4
- 6.15.5
- 6.15.6
- 6.15.7
- 6.15.8
- 6.15.9
- 6.15.10
- 6.16.0
- 6.16.1
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.1
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 261565
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-38715
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.4.297/5.10.241/5.15.190/6.1.149/6.6.103/6.12.43/6.15.11/6.16.2/6.17-rc1
Patch: e7d2dc2421e821e4045775e6dc226378328de6f6/67ecc81f6492275c9c54280532f558483c99c90e/a1a60e79502279f996e55052f50cc14919020475/fe2891a9c43ab87d1a210d61e6438ca6936e2f62/384a66b89f9540a9a8cb0f48807697dfabaece4c/efc095b35b23297e419c2ab4fc1ed1a8f0781a29/fc7f732984ec91f30be3e574e0644066d07f2b78/eec522fd0d28106b14a59ab2d658605febe4a3bb/a431930c9bac518bf99d6b1da526a7f37ddee8d8
Timeline
04/16/2025 CVE reserved09/04/2025 Advisory disclosed
09/04/2025 VulDB entry created
02/10/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2025-38715 (🔒)
GCVE (CVE): GCVE-0-2025-38715
GCVE (VulDB): GCVE-100-322573
CERT Bund: WID-SEC-2025-1976 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 09/04/2025 18:32Updated: 02/10/2026 07:22
Changes: 09/04/2025 18:32 (59), 09/05/2025 20:19 (7), 09/07/2025 22:35 (2), 10/08/2025 18:36 (1), 12/09/2025 18:13 (1), 01/15/2026 03:05 (1), 01/27/2026 18:02 (11), 02/10/2026 07:22 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.