CVE-2026-23141: Linux kernel · btrfs: send: check for inline extents in range_is_hole_in_parent()
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1112.119~20.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.15.0-1112.119~20.04.1, 5.15.0-1117.126~20.04.1, 5.15.0-1117.126~20.04.2 +70
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-8278-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8289-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8296-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8296-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8289-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8278-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8393-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8440-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8499-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8570-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8575-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8576-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 25.10linuxpkg:deb/ubuntu/linux?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-oraclepkg:deb/ubuntu/linux-oracle?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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
- ubuntu.com/security/CVE-2026-23141 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-23141 (opens in a new tab)
- git.kernel.org/linus/08b096c1372cd69627f4f559fb47c9fb67a52b39 (opens in a new tab)
- git.kernel.org/stable/c/08b096c1372cd69627f4f559fb47c9fb67a52b39 (opens in a new tab)
- git.kernel.org/stable/c/39f83f10772310ba4a77f2b5256aaf36994ef7e8 (opens in a new tab)
- git.kernel.org/stable/c/db00636643e66898d79f2530ac9c56ebd5eca369 (opens in a new tab)
- git.kernel.org/stable/c/f2dc6ab3a14c2d2eb0b14783427eb9b03bf631c9 (opens in a new tab)
- ubuntu.com/security/notices/USN-8278-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8289-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8296-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8296-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8289-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8278-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8393-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8440-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8499-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8570-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8575-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8576-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8594-1 (opens in a new tab)