CVE-2026-23141: Linux kernel · btrfs: send: check for inline extents in range_is_hole_in_parent()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f2dc6ab3a14c2d2eb0b14783427eb9b03bf631c9 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 21:34 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in f2dc6ab3a14c2d2eb0b14783427eb9b03bf631c9, db00636643e66898d79f2530ac9c56ebd5eca369, d948055bd46a9c14d1d4217aed65c5c258c32903 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 14 Feb 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 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
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.
References
- git.kernel.org/stable/c/901e581bfc44d181f7d9c3f11880dac3e89deb2e (opens in a new tab)
- git.kernel.org/stable/c/d948055bd46a9c14d1d4217aed65c5c258c32903 (opens in a new tab)
- git.kernel.org/stable/c/f2dc6ab3a14c2d2eb0b14783427eb9b03bf631c9 (opens in a new tab)
- git.kernel.org/stable/c/db00636643e66898d79f2530ac9c56ebd5eca369 (opens in a new tab)
- git.kernel.org/stable/c/39f83f10772310ba4a77f2b5256aaf36994ef7e8 (opens in a new tab)
- git.kernel.org/stable/c/08b096c1372cd69627f4f559fb47c9fb67a52b39 (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)