From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2023-53448: fbdev: imxfb: Removed unneeded release_mem_region
Date: Wed, 1 Oct 2025 13:42:18 +0200 [thread overview]
Message-ID: <2025100102-CVE-2023-53448-e125@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
fbdev: imxfb: Removed unneeded release_mem_region
Remove unnecessary release_mem_region from the error path to prevent
mem region from being released twice, which could avoid resource leak
or other unexpected issues.
The Linux kernel CVE team has assigned CVE-2023-53448 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.0 with commit b083c22d51148f3d3028291343196471be5d9f36 and fixed in 6.1.42 with commit 6aa851f6276fa08cd59b044bc2b803c49edf58a2
Issue introduced in 6.0 with commit b083c22d51148f3d3028291343196471be5d9f36 and fixed in 6.4.7 with commit 38282a92c30422836d49e519bd109237f86a0888
Issue introduced in 6.0 with commit b083c22d51148f3d3028291343196471be5d9f36 and fixed in 6.5 with commit 45fcc058a75bf5d65cf4c32da44a252fbe873cd4
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-53448
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/video/fbdev/imxfb.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/6aa851f6276fa08cd59b044bc2b803c49edf58a2
https://git.kernel.org/stable/c/38282a92c30422836d49e519bd109237f86a0888
https://git.kernel.org/stable/c/45fcc058a75bf5d65cf4c32da44a252fbe873cd4
reply other threads:[~2025-10-01 11:52 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=2025100102-CVE-2023-53448-e125@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.