From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89982: i2c: mux: Fix channel node leak on adapter add failure
Date: Wed, 16 Sep 2026 11:31:52 +0100 [thread overview]
Message-ID: <2026091656-CVE-2026-89982-e001@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
i2c: mux: Fix channel node leak on adapter add failure
i2c_mux_add_adapter() takes a reference to the Device Tree channel node
before registering the new adapter. If adapter registration fails, the
error path frees the private data without dropping that reference.
Release the channel node before freeing the private data.
The Linux kernel CVE team has assigned CVE-2026-89982 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.5 with commit bc45449b1444611d68466ae7f45f235420d79019 and fixed in 5.10.270 with commit 4f42f70afd2447f3c82ca69d1e03466a75348ba9
Issue introduced in 3.5 with commit bc45449b1444611d68466ae7f45f235420d79019 and fixed in 5.15.221 with commit 4c9bc46a2a4afb7a11c48d33bdf19febab431015
Issue introduced in 3.5 with commit bc45449b1444611d68466ae7f45f235420d79019 and fixed in 6.1.188 with commit dd2c1e6747b17b24ecddd48a7bb6bb964c2793d1
Issue introduced in 3.5 with commit bc45449b1444611d68466ae7f45f235420d79019 and fixed in 6.6.157 with commit 0927153f2abf48b6cc3e5f27063a17f7a8d47f38
Issue introduced in 3.5 with commit bc45449b1444611d68466ae7f45f235420d79019 and fixed in 6.12.110 with commit b580f062b24c4eef562f08f210c028adb34ef14e
Issue introduced in 3.5 with commit bc45449b1444611d68466ae7f45f235420d79019 and fixed in 6.18.51 with commit 2b3b06cb709c4bf75a3fe3da3a0ca368ee3b40e5
Issue introduced in 3.5 with commit bc45449b1444611d68466ae7f45f235420d79019 and fixed in 7.2.5 with commit 694e7e6edf249723ca7d3ef77c2ca1badfc78dc4
Issue introduced in 3.5 with commit bc45449b1444611d68466ae7f45f235420d79019 and fixed in 7.3-rc1 with commit 385c7af4e3b95d0769fd211831674e83b16a2ebf
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-89982
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/i2c/i2c-mux.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/4f42f70afd2447f3c82ca69d1e03466a75348ba9
https://git.kernel.org/stable/c/4c9bc46a2a4afb7a11c48d33bdf19febab431015
https://git.kernel.org/stable/c/dd2c1e6747b17b24ecddd48a7bb6bb964c2793d1
https://git.kernel.org/stable/c/0927153f2abf48b6cc3e5f27063a17f7a8d47f38
https://git.kernel.org/stable/c/b580f062b24c4eef562f08f210c028adb34ef14e
https://git.kernel.org/stable/c/2b3b06cb709c4bf75a3fe3da3a0ca368ee3b40e5
https://git.kernel.org/stable/c/694e7e6edf249723ca7d3ef77c2ca1badfc78dc4
https://git.kernel.org/stable/c/385c7af4e3b95d0769fd211831674e83b16a2ebf
reply other threads:[~2026-09-16 10:42 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=2026091656-CVE-2026-89982-e001@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.