CVE-2026-23043: btrfs: fix NULL pointer dereference in do_abort_log_replay()
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix NULL pointer dereference in do_abort_log_replay()
Coverity reported a NULL pointer dereference issue (CID 1666756) in
do_abort_log_replay(). When btrfs_alloc_path() fails in
replay_one_buffer(), wc->subvol_path is NULL, but btrfs_abort_log_replay()
calls do_abort_log_replay() which unconditionally dereferences
wc->subvol_path when attempting to print debug information. Fix this by
adding a NULL check before dereferencing wc->subvol_path in
do_abort_log_replay().
Security readout for executives and security teams
Plain-English summary
CVE-2026-23043 is a Linux kernel Btrfs bug where an error-handling path can crash by dereferencing a missing subvolume path while aborting log replay. The sources describe a reliability issue, not data theft or remote compromise. Severity is not provided.
Executive priority
Handle through normal kernel patch management unless critical systems depend on Btrfs. There is no provided evidence of exploitation, but affected storage workloads could experience availability impact if the bug is reached.
Technical view
In Btrfs do_abort_log_replay(), wc->subvol_path could be NULL after btrfs_alloc_path() fails in replay_one_buffer(). btrfs_abort_log_replay() then called debug-print logic that dereferenced it. The kernel fix adds a NULL check before dereferencing wc->subvol_path.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with Btrfs in use. The bundle lists Linux 6.18, 6.18.6, and 6.19-related version data, but distro backports may change exposure. Confirm against vendor kernel advisories.
Exploitation context
The source bundle does not report active exploitation, and KEV is false. It describes a NULL pointer dereference discovered by Coverity in a Btrfs log replay abort path. No public source provided exploit prerequisites beyond the allocation-failure scenario.
Researcher notes
The key evidence is the kernel fix description: allocation failure leaves wc->subvol_path NULL, and abort logging dereferenced it. Missing data includes CVSS, CWE, exploitability analysis, and precise distro package ranges.
Mitigation direction
Update to a Linux kernel containing the referenced stable fixes.
Check your Linux distribution advisory for backported kernel packages.
Prioritize systems using Btrfs for root, data, or critical workloads.
Monitor vendor guidance for any additional operational mitigations.
Validation and detection
Inventory Linux hosts using Btrfs filesystems.
Map running kernel builds to vendor fixed package versions.
Confirm the referenced stable commits are present or backported.
Review crash logs for Btrfs log replay or NULL dereference symptoms.
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-23043 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
3Source 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 4, 2026, 16:00 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.