Answer in brief
CVE-2025-71184 records a Medium severity (CVSS 5.5) vulnerability in btrfs: fix NULL dereference on root when tracing inode eviction. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:2.6.39:-:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.19:rc8:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1abe9b8a138c9988ba8f7bfded6453649a31541f <99181ddb124cfe2b09f5e924c308222d2339e82a || >=1abe9b8a138c9988ba8f7bfded6453649a31541f <64d8abd8c5305795a2b35fc96039d99d34f5e762 || >=1abe9b8a138c9988ba8f7bfded6453649a31541f <582ba48e4a4c06fef6bdcf4e57b7b9af660bbd0c || >=1abe9b8a138c9988ba8f7bfded6453649a31541f <99e057f3d3ef24b99a7b1d84e01dd1bd890098da || >=1abe9b8a138c9988ba8f7bfded6453649a31541f <f157dd661339fc6f5f2b574fe2429c43bd309534 | 99181ddb124cfe2b09f5e924c308222d2339e82a, 64d8abd8c5305795a2b35fc96039d99d34f5e762, 582ba48e4a4c06fef6bdcf4e57b7b9af660bbd0c, 99e057f3d3ef24b99a7b1d84e01dd1bd890098da, f157dd661339fc6f5f2b574fe2429c43bd309534 |
| Linux/Linuxgeneric | 2.6.39 | Not reported |
Published upstream
Jan 31, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 30, 2026
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix NULL dereference on root when tracing inode eviction When evicting an inode the first thing we do is to setup tracing for it, which implies fetching the root's id. But in btrfs_evict_inode() the root might be NULL, as implied in the next check that we do in btrfs_evict_inode(). Hence, we either should set the ->root_objectid to 0 in case the root is NULL, or we move tracing setup after checking that the root is not NULL. Setting the rootid to 0 at least gives us the possibility to trace this call even in the case when the root is NULL, so that's the solution taken here.
Quoted source text, attributed separately from HOL analysis.