VulnerabilityPublished 18 Jun 2025Updated 30 Oct 2026

CVE-2025-38059: Linux kernel · btrfs: avoid NULL pointer dereference if no valid csum tree

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in f95d186255b319c48a365d47b69bd997fecb674e : 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 f95d186255b319c48a365d47b69bd997fecb674e, d35bed14b0bc95c6845863a3744ecd10b888c830, 50d0de59f66cbe6d597481e099bf1c70fd07e0a9 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Jun 2025
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 ≥ 74ef00185eb864252156022ff129b01549504175, < f95d186255b319c48a365d47b69bd997fecb674e	Fixed in f95d186255b319c48a365d47b69bd997fecb674e
LinuxLinux	Affected ≥ 74ef00185eb864252156022ff129b01549504175, < d35bed14b0bc95c6845863a3744ecd10b888c830	Fixed in d35bed14b0bc95c6845863a3744ecd10b888c830
LinuxLinux	Affected ≥ 74ef00185eb864252156022ff129b01549504175, < 50d0de59f66cbe6d597481e099bf1c70fd07e0a9	Fixed in 50d0de59f66cbe6d597481e099bf1c70fd07e0a9
LinuxLinux	Affected ≥ 74ef00185eb864252156022ff129b01549504175, < 6e9770de024964b1017f99ee94f71967bd6edaeb	Fixed in 6e9770de024964b1017f99ee94f71967bd6edaeb
LinuxLinux	Affected ≥ 74ef00185eb864252156022ff129b01549504175, < 2db25048a61c0909459b074af04e06ab8a8b939e	Fixed in 2db25048a61c0909459b074af04e06ab8a8b939e
LinuxLinux	Affected =5.9	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: avoid NULL pointer dereference if no valid csum tree [BUG] When trying read-only scrub on a btrfs with rescue=idatacsums mount option, it will crash with the following call trace: BUG: kernel NULL pointer dereference, address: 0000000000000208 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page CPU: 1 UID: 0 PID: 835 Comm: btrfs Tainted: G O 6.15.0-rc3-custom+ #236 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 02/02/2022 RIP: 0010:btrfs_lookup_csums_bitmap+0x49/0x480 [btrfs] Call Trace: <TASK> scrub_find_fill_first_stripe+0x35b/0x3d0 [btrfs] scrub_simple_mirror+0x175/0x290 [btrfs] scrub_stripe+0x5f7/0x6f0 [btrfs] scrub_chunk+0x9a/0x150 [btrfs] scrub_enumerate_chunks+0x333/0x660 [btrfs] btrfs_scrub_dev+0x23e/0x600 [btrfs] btrfs_ioctl+0x1dcf/0x2f80 [btrfs] __x64_sys_ioctl+0x97/0xc0 do_syscall_64+0x4f/0x120 entry_SYSCALL_64_after_hwframe+0x76/0x7e [CAUSE] Mount option "rescue=idatacsums" will completely skip loading the csum tree, so that any data read will not find any data csum thus we will ignore data checksum verification. Normally call sites utilizing csum tree will check the fs state flag NO_DATA_CSUMS bit, but unfortunately scrub does not check that bit at all. This results in scrub to call btrfs_search_slot() on a NULL pointer and triggered above crash. [FIX] Check both extent and csum tree root before doing any tree search.

References

Community reviews

Loading reviews…