CVE-2026-23465: Linux kernel · btrfs: log new dentries when logging parent dir of a conflicting inode
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f556b1e09d054e31f464c0fd37280c2b5a393fee : patch Linux kernel soon.
Data as of 30 Oct 2026, 12:48 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- Patch
- Available – fixed in f556b1e09d054e31f464c0fd37280c2b5a393fee, 9573a365ff9ff45da9222d3fe63695ce562beb24, 56e72c8b02d982be775d9df025357c152383ee84 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 3 Apr 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 30 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
|
AI-suggested
A fix is available in the Linux kernel as indicated by the presence of multiple fixed commit versions. Users should update their Linux kernel to a version that includes these fixes to prevent data loss related to this issue.
Description
A vulnerability in the Linux kernel's btrfs filesystem logging mechanism causes new directory entries (dentries) to not be logged when logging the parent directory of a conflicting inode. This can lead to missing directory entries after a power failure and log replay, resulting in data loss for those entries.
References
- git.kernel.org/stable/c/6c23595c54cfeb878e3fbbb8eb08bc5061d0c2d4 (opens in a new tab)
- git.kernel.org/stable/c/56e72c8b02d982be775d9df025357c152383ee84 (opens in a new tab)
- git.kernel.org/stable/c/f556b1e09d054e31f464c0fd37280c2b5a393fee (opens in a new tab)
- git.kernel.org/stable/c/1cf30c73602c69d750c9345c47f2c0e9d0cfb578 (opens in a new tab)
- git.kernel.org/stable/c/6f5a51969b1deb79aefd2194b48fe7e78e72ff7e (opens in a new tab)
- git.kernel.org/stable/c/9573a365ff9ff45da9222d3fe63695ce562beb24 (opens in a new tab)