From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43419: ceph: fix memory leaks in ceph_mdsc_build_path()
Date: Fri, 8 May 2026 16:22:28 +0200 [thread overview]
Message-ID: <2026050846-CVE-2026-43419-1421@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ceph: fix memory leaks in ceph_mdsc_build_path()
Add __putname() calls to error code paths that did not free the "path"
pointer obtained by __getname(). If ownership of this pointer is not
passed to the caller via path_info.path, the function must free it
before returning.
The Linux kernel CVE team has assigned CVE-2026-43419 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.6 with commit 3fd945a79e147ee10f84213976889b29049c3519 and fixed in 6.6.130 with commit 657dc653b06a3cc0282aea447a3f137fa94066a4
Issue introduced in 6.6 with commit 3fd945a79e147ee10f84213976889b29049c3519 and fixed in 6.12.78 with commit 5895d0164c84d7fec6abc198920c257f55c51899
Issue introduced in 6.6 with commit 3fd945a79e147ee10f84213976889b29049c3519 and fixed in 6.18.19 with commit 097cd68f46686391a98f2618188f0cb7b7570de2
Issue introduced in 6.6 with commit 3fd945a79e147ee10f84213976889b29049c3519 and fixed in 6.19.9 with commit 13b8b9d6f59ef17fb96c298c3a0d62a8306950cc
Issue introduced in 6.6 with commit 3fd945a79e147ee10f84213976889b29049c3519 and fixed in 7.0 with commit 040d159a45ded7f33201421a81df0aa2a86e5a0b
Issue introduced in 5.10.234 with commit 0f2b2d9e881c90402dbe28f9ba831775b7992e1f
Issue introduced in 5.15.177 with commit d42ad3f161a5a487f81915c406f46943c7187a0a
Issue introduced in 6.1.125 with commit e4b168c64da06954be5d520f6c16469b1cadc069
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-43419
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/ceph/mds_client.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/657dc653b06a3cc0282aea447a3f137fa94066a4
https://git.kernel.org/stable/c/5895d0164c84d7fec6abc198920c257f55c51899
https://git.kernel.org/stable/c/097cd68f46686391a98f2618188f0cb7b7570de2
https://git.kernel.org/stable/c/13b8b9d6f59ef17fb96c298c3a0d62a8306950cc
https://git.kernel.org/stable/c/040d159a45ded7f33201421a81df0aa2a86e5a0b
reply other threads:[~2026-05-08 14:25 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=2026050846-CVE-2026-43419-1421@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