From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2023-53579: gpio: mvebu: fix irq domain leak
Date: Sat, 4 Oct 2025 17:17:33 +0200 [thread overview]
Message-ID: <2025100455-CVE-2023-53579-e030@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
gpio: mvebu: fix irq domain leak
Uwe Kleine-König pointed out we still have one resource leak in the mvebu
driver triggered on driver detach. Let's address it with a custom devm
action.
The Linux kernel CVE team has assigned CVE-2023-53579 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.9 with commit 812d47889a8e418d7bea9bec383581a34c19183e and fixed in 5.15.124 with commit b19e90521286a03bc3793fd598f20277a8f99c85
Issue introduced in 4.9 with commit 812d47889a8e418d7bea9bec383581a34c19183e and fixed in 6.1.43 with commit 44e2afbf650f3264519643fcc9e6b4d2f6e8d547
Issue introduced in 4.9 with commit 812d47889a8e418d7bea9bec383581a34c19183e and fixed in 6.4.8 with commit d9b791d8362359d241b4e8f4b4767c681ffdb6ef
Issue introduced in 4.9 with commit 812d47889a8e418d7bea9bec383581a34c19183e and fixed in 6.5 with commit 644ee70267a934be27370f9aa618b29af7290544
Issue introduced in 3.16.40 with commit f0cde54863da281cec1ed85497b4ec58d29c1460
Issue introduced in 4.8.9 with commit 7a9239fd04802ee6ddf82d211cff3ee7df9c473a
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-2023-53579
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/gpio/gpio-mvebu.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/b19e90521286a03bc3793fd598f20277a8f99c85
https://git.kernel.org/stable/c/44e2afbf650f3264519643fcc9e6b4d2f6e8d547
https://git.kernel.org/stable/c/d9b791d8362359d241b4e8f4b4767c681ffdb6ef
https://git.kernel.org/stable/c/644ee70267a934be27370f9aa618b29af7290544
reply other threads:[~2025-10-04 15:19 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=2025100455-CVE-2023-53579-e030@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.