From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-45863: i3c: dw: Fix memory leak in dw_i3c_master_i2c_xfers()
Date: Wed, 27 May 2026 14:18:25 +0200 [thread overview]
Message-ID: <2026052711-CVE-2026-45863-a8fa@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
i3c: dw: Fix memory leak in dw_i3c_master_i2c_xfers()
The dw_i3c_master_i2c_xfers() function allocates memory for the xfer
structure using dw_i3c_master_alloc_xfer(). If pm_runtime_resume_and_get()
fails, the function returns without freeing the allocated xfer, resulting
in a memory leak.
Add a dw_i3c_master_free_xfer() call to the error path to ensure the
allocated memory is properly freed.
Compile tested only. Issue found using a prototype static analysis tool
and code review.
The Linux kernel CVE team has assigned CVE-2026-45863 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.11 with commit 62fe9d06f5709caa1fa68055873ff279e05ade37 and fixed in 6.12.75 with commit 140a45bd4f6db7d1b30cab967d29689b946c52fa
Issue introduced in 6.11 with commit 62fe9d06f5709caa1fa68055873ff279e05ade37 and fixed in 6.18.14 with commit 8e71414e252c1cb235911008a98fd47927d3a55c
Issue introduced in 6.11 with commit 62fe9d06f5709caa1fa68055873ff279e05ade37 and fixed in 6.19.4 with commit a2c41467ef42f69a3958493a0395ba75174710dc
Issue introduced in 6.11 with commit 62fe9d06f5709caa1fa68055873ff279e05ade37 and fixed in 7.0 with commit 2537089413514caaa9a5fdeeac3a34d45100f747
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-45863
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/i3c/master/dw-i3c-master.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/140a45bd4f6db7d1b30cab967d29689b946c52fa
https://git.kernel.org/stable/c/8e71414e252c1cb235911008a98fd47927d3a55c
https://git.kernel.org/stable/c/a2c41467ef42f69a3958493a0395ba75174710dc
https://git.kernel.org/stable/c/2537089413514caaa9a5fdeeac3a34d45100f747
reply other threads:[~2026-05-27 12:20 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=2026052711-CVE-2026-45863-a8fa@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.