CVE-2025-38382: btrfs: fix iteration of extrefs during log replay
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.20% (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 2d11d274e2e1d7c79e2ca8461ce3ff3a95c11171, 539969fc472886a1d63565459514d47e27fef461, 54a7081ed168b72a8a2d6ef4ba3a1259705a2926; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 2d11d274e2e1d7c79e2ca8461ce3ff3a95c11171, 539969fc472886a1d63565459514d47e27fef461, 54a7081ed168b72a8a2d6ef4ba3a1259705a2926; 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: 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.
- Published
- Jul 25, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-908
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.2%
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 kernel6.1.57 and later · before 6.1.144
- linux linux kernel6.2 and later · before 6.6.97
- linux linux kernel6.7 and later · before 6.12.37
- linux linux kernel6.13 and later · before 6.15.6
- linux linux kernel6.16
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
- 6.2affected
- 1cf474cd474bc5d3ef63086ffd009a87a5b7bb2e and later · before 539969fc472886a1d63565459514d47e27fef461affected · git
- e43eec81c5167b655b72c781b0e75e62a05e415e and later · before 2d11d274e2e1d7c79e2ca8461ce3ff3a95c11171affected · git
- e43eec81c5167b655b72c781b0e75e62a05e415e and later · before 7ac790dc2ba00499a8d671d4a24de4d4ad27e234affected · git
- e43eec81c5167b655b72c781b0e75e62a05e415e and later · before aee57a0293dca675637e5504709f9f8fd8e871beaffected · git
- e43eec81c5167b655b72c781b0e75e62a05e415e and later · before 54a7081ed168b72a8a2d6ef4ba3a1259705a2926affected · git
- 6.1.57 and later · before 6.1.144affected · semver
- before 6.2not affected · semver
- 6.1.144 and later · up to and including 6.1.*not affected · semver
- 6.6.97 and later · up to and including 6.6.*not affected · semver
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.147-1 | 6.1.147-1 |
| Debian:13 | linux | before 6.12.37-1 | 6.12.37-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-38379Jul 25, 2025 · smb: client: fix warning when reconnecting channel22Monitor
- ← EarlierCVE-2025-38381Jul 25, 2025 · Input: cs40l50-vibra - fix potential NULL dereference in cs40l50_upload_owt()22Monitor
- Later →CVE-2025-38383Jul 25, 2025 · mm/vmalloc: fix data race in show_numa_info()18Monitor
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 | 2d11d274e2e1d7c79e2ca8461ce3ff3a95c11171 | Vendor (CNA) |
| Linux Linux | 539969fc472886a1d63565459514d47e27fef461 | Vendor (CNA) |
| Linux Linux | 54a7081ed168b72a8a2d6ef4ba3a1259705a2926 | Vendor (CNA) |
| Linux Linux | 6.1.144 | Vendor (CNA) |
| Linux Linux | 7ac790dc2ba00499a8d671d4a24de4d4ad27e234 | Vendor (CNA) |
| Linux Linux | aee57a0293dca675637e5504709f9f8fd8e871be | 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.147-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.
- CVE-2024-50302248 days apartHID: core: zero-initialize the report bufferKEV52Plan
- CVE-2026-52989334 days apartnvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers39Monitor
- CVE-2024-47685277 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()36Monitor
- CVE-2026-53225335 days apartsctp: fix uninit-value in __sctp_rcv_asconf_lookup()36Monitor
- CVE-2026-53170335 days apartaccel/ethosu: reject DMA commands with uninitialized length35Monitor
- CVE-2026-43139285 days apartxfrm6: fix uninitialized saddr in xfrm6_get_saddr()34Monitor
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-908 · Use of Uninitialized ResourceCVSS 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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/539969fc472886a1d63565459514d47e27fef461
- git.kernel.org/stable/c/54a7081ed168b72a8a2d6ef4ba3a1259705a2926
- git.kernel.org/stable/c/7ac790dc2ba00499a8d671d4a24de4d4ad27e234
- git.kernel.org/stable/c/aee57a0293dca675637e5504709f9f8fd8e871be
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.