From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49392: serial: 8250_aspeed_vuart: Fix potential NULL dereference in aspeed_vuart_probe
Date: Wed, 26 Feb 2025 03:11:06 +0100 [thread overview]
Message-ID: <2025022649-CVE-2022-49392-59db@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
serial: 8250_aspeed_vuart: Fix potential NULL dereference in aspeed_vuart_probe
platform_get_resource() may fail and return NULL, so we should
better check it's return value to avoid a NULL pointer dereference.
The Linux kernel CVE team has assigned CVE-2022-49392 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.14 with commit 54da3e381c2b55289b220601f403f17df7b20597 and fixed in 5.15.47 with commit 923d34ce069e8e51a4d003caa6b66a8cd6ecd0ed
Issue introduced in 5.14 with commit 54da3e381c2b55289b220601f403f17df7b20597 and fixed in 5.17.15 with commit 90a6b6fc52bfdcfe9698454bf5bea26112abbcd1
Issue introduced in 5.14 with commit 54da3e381c2b55289b220601f403f17df7b20597 and fixed in 5.18.4 with commit d5f1275f101e0e8a172d300d897f5a12e87e3485
Issue introduced in 5.14 with commit 54da3e381c2b55289b220601f403f17df7b20597 and fixed in 5.19 with commit 0e0fd55719fa081de6f9e5d9e6cef48efb04d34a
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-2022-49392
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/tty/serial/8250/8250_aspeed_vuart.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/923d34ce069e8e51a4d003caa6b66a8cd6ecd0ed
https://git.kernel.org/stable/c/90a6b6fc52bfdcfe9698454bf5bea26112abbcd1
https://git.kernel.org/stable/c/d5f1275f101e0e8a172d300d897f5a12e87e3485
https://git.kernel.org/stable/c/0e0fd55719fa081de6f9e5d9e6cef48efb04d34a
reply other threads:[~2025-02-26 2:13 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=2025022649-CVE-2022-49392-59db@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@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.