From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43393: btrfs: fix chunk map leak in btrfs_map_block() after btrfs_chunk_map_num_copies()
Date: Fri, 8 May 2026 16:22:02 +0200 [thread overview]
Message-ID: <2026050837-CVE-2026-43393-8c6d@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix chunk map leak in btrfs_map_block() after btrfs_chunk_map_num_copies()
Fix a chunk map leak in btrfs_map_block(): if we return early with -EINVAL,
we're not freeing the chunk map that we've just looked up.
The Linux kernel CVE team has assigned CVE-2026-43393 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit 0ae653fbec2b9fbc72c65a0c99528990bfb2136d and fixed in 6.12.78 with commit 0e4aaf5a3212b6a469c2489637c29a8e2a5062a5
Issue introduced in 6.12 with commit 0ae653fbec2b9fbc72c65a0c99528990bfb2136d and fixed in 6.18.19 with commit 7bdf00ed75c477252578068dba19934cd825f20a
Issue introduced in 6.12 with commit 0ae653fbec2b9fbc72c65a0c99528990bfb2136d and fixed in 6.19.9 with commit 4f90c5c2698383984102401b1724b0b67da832ab
Issue introduced in 6.12 with commit 0ae653fbec2b9fbc72c65a0c99528990bfb2136d and fixed in 7.0 with commit f15fb3d41543244d1179f423da4a4832a55bc050
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-43393
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/volumes.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/0e4aaf5a3212b6a469c2489637c29a8e2a5062a5
https://git.kernel.org/stable/c/7bdf00ed75c477252578068dba19934cd825f20a
https://git.kernel.org/stable/c/4f90c5c2698383984102401b1724b0b67da832ab
https://git.kernel.org/stable/c/f15fb3d41543244d1179f423da4a4832a55bc050
reply other threads:[~2026-05-08 14:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026050837-CVE-2026-43393-8c6d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox