VulnerabilityPublished 31 Jan 2026Updated 30 Oct 2026

CVE-2025-71184: Linux kernel · btrfs: fix NULL dereference on root when tracing inode eviction

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in f157dd661339fc6f5f2b574fe2429c43bd309534 : update Linux kernel when convenient.

Data as of 30 Oct 2026, 12:33 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Patch: Available – fixed in f157dd661339fc6f5f2b574fe2429c43bd309534, 99181ddb124cfe2b09f5e924c308222d2339e82a, 582ba48e4a4c06fef6bdcf4e57b7b9af660bbd0c +2

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 1abe9b8a138c9988ba8f7bfded6453649a31541f, < f157dd661339fc6f5f2b574fe2429c43bd309534	Fixed in f157dd661339fc6f5f2b574fe2429c43bd309534
LinuxLinux	Affected ≥ 1abe9b8a138c9988ba8f7bfded6453649a31541f, < 99181ddb124cfe2b09f5e924c308222d2339e82a	Fixed in 99181ddb124cfe2b09f5e924c308222d2339e82a
LinuxLinux	Affected ≥ 1abe9b8a138c9988ba8f7bfded6453649a31541f, < 582ba48e4a4c06fef6bdcf4e57b7b9af660bbd0c	Fixed in 582ba48e4a4c06fef6bdcf4e57b7b9af660bbd0c
LinuxLinux	Affected ≥ 1abe9b8a138c9988ba8f7bfded6453649a31541f, < 99e057f3d3ef24b99a7b1d84e01dd1bd890098da	Fixed in 99e057f3d3ef24b99a7b1d84e01dd1bd890098da
LinuxLinux	Affected ≥ 1abe9b8a138c9988ba8f7bfded6453649a31541f, < 64d8abd8c5305795a2b35fc96039d99d34f5e762	Fixed in 64d8abd8c5305795a2b35fc96039d99d34f5e762
LinuxLinux	Affected =2.6.39	Fixed in–

Description

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.

References

Community reviews

Loading reviews…