CVE-2026-89644: Linux kernel · btrfs: fix extent map leak in NOCOW direct I/O write
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f42efd634c0ae7ba0ce2fc5e30e291b0803b0ae2 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f42efd634c0ae7ba0ce2fc5e30e291b0803b0ae2, cb732d302245b14943a5017015fffa8e6db7a6c0, b7c873765875645b11503f94c9bae2ca80127375 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Sep 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.
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: fix extent map leak in NOCOW direct I/O write btrfs_dio_iomap_begin() calls btrfs_get_extent(), which returns an extent map reference that must be dropped on all exit paths. For direct writes into a NOCOW range, btrfs_get_blocks_direct_write() keeps using that extent map and asks btrfs_create_dio_extent() to allocate the ordered extent. If that fails, for example because btrfs_alloc_ordered_extent() fails, the function returns the error without dropping the input extent map. The PREALLOC path avoided this by dropping the input extent map before replacing it with the newly created one. Check the error from btrfs_create_dio_extent() before replacing the map and drop the input extent map on failure.
References
- git.kernel.org/stable/c/cb732d302245b14943a5017015fffa8e6db7a6c0 (opens in a new tab)
- git.kernel.org/stable/c/b7c873765875645b11503f94c9bae2ca80127375 (opens in a new tab)
- git.kernel.org/stable/c/f42efd634c0ae7ba0ce2fc5e30e291b0803b0ae2 (opens in a new tab)
- git.kernel.org/stable/c/05a1a816eef8b3e4332620a64fc8cf45c4eb5c0d (opens in a new tab)
- git.kernel.org/stable/c/3f950867c307c5413d628a153ac44915bd117ffd (opens in a new tab)