[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2026020439-CVE-2026-23043-4975@gregkh>
Date: Wed, 4 Feb 2026 17:00:43 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2026-23043: btrfs: fix NULL pointer dereference in do_abort_log_replay()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
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().
The Linux kernel CVE team has assigned CVE-2026-23043 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18 with commit 2753e49176240f21e4bb10e03514f99e732704bb and fixed in 6.18.6 with commit 6d1b61b8e1e44888c643d89225ab819b10649b2e
Issue introduced in 6.18 with commit 2753e49176240f21e4bb10e03514f99e732704bb and fixed in 6.19-rc5 with commit 530e3d4af566ca44807d79359b90794dea24c4f3
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-23043
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/btrfs/tree-log.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/6d1b61b8e1e44888c643d89225ab819b10649b2e
https://git.kernel.org/stable/c/530e3d4af566ca44807d79359b90794dea24c4f3
Powered by blists - more mailing lists