From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43317: most: core: fix leak on early registration failure
Date: Fri, 8 May 2026 15:26:20 +0200 [thread overview]
Message-ID: <2026050818-CVE-2026-43317-a9bf@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
most: core: fix leak on early registration failure
A recent commit fixed a resource leak on early registration failures but
for some reason left out the first error path which still leaks the
resources associated with the interface.
Fix up also the first error path so that the interface is always
released on errors.
The Linux kernel CVE team has assigned CVE-2026-43317 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.6 with commit 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c and fixed in 6.12.75 with commit bbfe49ffb892bddf32c34bea95b7ff0fc30affb5
Issue introduced in 5.6 with commit 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c and fixed in 6.18.16 with commit f1ba620f9e8d7291f80c0554e4b820f5fb30e819
Issue introduced in 5.6 with commit 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c and fixed in 6.19.6 with commit 5fd4396c2e48e90cc2597a86c18227d56ea845f0
Issue introduced in 5.6 with commit 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c and fixed in 7.0 with commit 2c198c272f9c9213b0fdf6b4a879f445c574f416
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-43317
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:
drivers/most/core.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/bbfe49ffb892bddf32c34bea95b7ff0fc30affb5
https://git.kernel.org/stable/c/f1ba620f9e8d7291f80c0554e4b820f5fb30e819
https://git.kernel.org/stable/c/5fd4396c2e48e90cc2597a86c18227d56ea845f0
https://git.kernel.org/stable/c/2c198c272f9c9213b0fdf6b4a879f445c574f416
reply other threads:[~2026-05-08 13:26 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=2026050818-CVE-2026-43317-a9bf@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