Linux Kernel up to 6.16-rc4 btrfs __inode_add_ref initialization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Linux Kernel up to 6.1.143/6.6.96/6.12.36/6.15.5/6.16-rc4. This affects the function __inode_add_ref of the component btrfs. Performing a manipulation results in initialization. This vulnerability is known as CVE-2025-38382. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 6.1.143/6.6.96/6.12.36/6.15.5/6.16-rc4. This affects the function __inode_add_ref of the component btrfs. The manipulation with an unknown input leads to a initialization vulnerability. CWE is classifying the issue as CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix iteration of extrefs during log replay At __inode_add_ref() when processing extrefs, if we jump into the next label we have an undefined value of victim_name.len, since we haven't initialized it before we did the goto. This results in an invalid memory access in the next iteration of the loop since victim_name.len was not initialized to the length of the name of the current extref. Fix this by initializing victim_name.len with the current extref's name length.

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2025-38382 since 04/16/2025. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 253428 (SUSE SLES15 Security Update : kernel (SUSE-SU-2025:02923-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.1.144, 6.6.97, 6.12.37, 6.15.6 or 6.16-rc5 eliminates this vulnerability. Applying the patch 539969fc472886a1d63565459514d47e27fef461/2d11d274e2e1d7c79e2ca8461ce3ff3a95c11171/7ac790dc2ba00499a8d671d4a24de4d4ad27e234/aee57a0293dca675637e5504709f9f8fd8e871be/54a7081ed168b72a8a2d6ef4ba3a1259705a2926 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 (253428) and CERT Bund (WID-SEC-2025-1653). Be aware that VulDB is the high quality source for vulnerability data.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • IBM QRadar SIEM
  • SUSE openSUSE
  • RESF Rocky Linux
  • Dell Avamar
  • Open Source Linux Kernel
  • Dell NetWorker
  • Dell Secure Connect Gateway

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Initialization
CWE: CWE-665
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 253428
Nessus Name: SUSE SLES15 Security Update : kernel (SUSE-SU-2025:02923-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.1.144/6.6.97/6.12.37/6.15.6/6.16-rc5
Patch: 539969fc472886a1d63565459514d47e27fef461/2d11d274e2e1d7c79e2ca8461ce3ff3a95c11171/7ac790dc2ba00499a8d671d4a24de4d4ad27e234/aee57a0293dca675637e5504709f9f8fd8e871be/54a7081ed168b72a8a2d6ef4ba3a1259705a2926

Timelineinfo

04/16/2025 CVE reserved
07/25/2025 +100 days Advisory disclosed
07/25/2025 +0 days VulDB entry created
01/03/2026 +162 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-38382 (🔒)
GCVE (CVE): GCVE-0-2025-38382
GCVE (VulDB): GCVE-100-317655
CERT Bund: WID-SEC-2025-1653 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 07/25/2025 15:41
Updated: 01/03/2026 16:16
Changes: 07/25/2025 15:41 (58), 08/19/2025 20:53 (7), 08/24/2025 01:47 (2), 09/14/2025 15:44 (1), 09/15/2025 18:59 (1), 09/28/2025 19:06 (1), 11/02/2025 07:12 (1), 11/17/2025 00:46 (1), 12/15/2025 20:35 (11), 01/03/2026 16:16 (1)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Interested in the pricing of exploits?

See the underground prices here!