CVE-2026-23141: btrfs: send: check for inline extents in range_is_hole_in_parent()
In the Linux kernel, the following vulnerability has been resolved:
btrfs: send: check for inline extents in range_is_hole_in_parent()
Before accessing the disk_bytenr field of a file extent item we need
to check if we are dealing with an inline extent.
This is because for inline extents their data starts at the offset of
the disk_bytenr field. So accessing the disk_bytenr
means we are accessing inline data or in case the inline data is less
than 8 bytes we can actually cause an invalid
memory access if this inline extent item is the first item in the leaf
or access metadata from other items.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23141 is a Linux kernel Btrfs bug in send handling. The kernel could read inline file extent data as if it were a disk address, causing invalid memory access or metadata reads. Business urgency depends on whether affected systems run Btrfs and use Btrfs send workflows.
Executive priority
Treat as a targeted kernel maintenance item, not an internet-wide emergency based on current evidence. Prioritize Btrfs-dependent servers and backup infrastructure, then follow normal kernel patch governance once vendor packages are available.
Technical view
The flaw is in Btrfs send range_is_hole_in_parent(). Before reading disk_bytenr from a file extent item, the code failed to confirm the extent was not inline. Inline extent data begins at that field offset, so the read can consume inline data, read adjacent metadata, or trigger invalid memory access.
Likely exposure
Exposure is most relevant to Linux systems using Btrfs, especially where Btrfs send operations are used. The source lists Linux kernel versions and stable branches as affected, but downstream distribution package status is not provided.
Exploitation context
The bundle does not cite active exploitation, KEV listing, public exploit availability, or a CVSS score. The described impact is invalid memory access or unintended metadata access during Btrfs send logic, but attacker prerequisites are not specified.
Researcher notes
Evidence is limited to the CVE record and Linux stable commit references. The record explains the vulnerable condition but does not define exploitability, required privileges, reachable attack paths, CVSS, or confirmed impact beyond invalid memory access or metadata access.
Mitigation direction
Check Linux distribution advisories for CVE-2026-23141 kernel updates.
Apply kernel updates containing the referenced stable commits when available.
Prioritize systems using Btrfs send or Btrfs-based backup workflows.
Reduce nonessential Btrfs send activity until vendor guidance is applied.
Validation and detection
Inventory Linux hosts using Btrfs filesystems.
Identify kernels matching the affected versions or missing referenced fixes.
Check whether Btrfs send is used in backup or replication jobs.
Confirm patched kernel packages include one of the referenced stable commits.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23141 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
7Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 14, 2026, 15:36 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.