From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49495: drm/msm/hdmi: check return value after calling platform_get_resource_byname()
Date: Wed, 26 Feb 2025 03:12:49 +0100 [thread overview]
Message-ID: <2025022606-CVE-2022-49495-7aba@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/hdmi: check return value after calling platform_get_resource_byname()
It will cause null-ptr-deref if platform_get_resource_byname() returns NULL,
we need check the return value.
Patchwork: https://patchwork.freedesktop.org/patch/482992/
The Linux kernel CVE team has assigned CVE-2022-49495 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.3 with commit c6a57a50ad562a2e6fc6ac3218b710caea73a58b and fixed in 4.9.318 with commit 9cb1ee33efccb8b107ee04b7b3441820de3fd2da
Issue introduced in 4.3 with commit c6a57a50ad562a2e6fc6ac3218b710caea73a58b and fixed in 4.14.283 with commit c1bfacf0daf25a5fc7d667399d6ff2dffda84cd8
Issue introduced in 4.3 with commit c6a57a50ad562a2e6fc6ac3218b710caea73a58b and fixed in 4.19.247 with commit 0978fcce91b90b561b8c82e7c492ba9fc8440eef
Issue introduced in 4.3 with commit c6a57a50ad562a2e6fc6ac3218b710caea73a58b and fixed in 5.4.198 with commit 2b3ed7547b1a052209da6c4ab886ffe0eed88c42
Issue introduced in 4.3 with commit c6a57a50ad562a2e6fc6ac3218b710caea73a58b and fixed in 5.10.121 with commit d9cb951d11a4ace4de5c50b1178ad211de17079e
Issue introduced in 4.3 with commit c6a57a50ad562a2e6fc6ac3218b710caea73a58b and fixed in 5.15.46 with commit 4cd66a8016b872a153bf892fe4258cbc0dacf5b1
Issue introduced in 4.3 with commit c6a57a50ad562a2e6fc6ac3218b710caea73a58b and fixed in 5.17.14 with commit 6369dda4a2209142ab819f01d3d2076d81e3ebdd
Issue introduced in 4.3 with commit c6a57a50ad562a2e6fc6ac3218b710caea73a58b and fixed in 5.18.3 with commit 9f5495a5c51c1d11c6ffc13aa2befffec0c2651a
Issue introduced in 4.3 with commit c6a57a50ad562a2e6fc6ac3218b710caea73a58b and fixed in 5.19 with commit a36e506711548df923ceb7ec9f6001375be799a5
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-49495
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/gpu/drm/msm/hdmi/hdmi.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/9cb1ee33efccb8b107ee04b7b3441820de3fd2da
https://git.kernel.org/stable/c/c1bfacf0daf25a5fc7d667399d6ff2dffda84cd8
https://git.kernel.org/stable/c/0978fcce91b90b561b8c82e7c492ba9fc8440eef
https://git.kernel.org/stable/c/2b3ed7547b1a052209da6c4ab886ffe0eed88c42
https://git.kernel.org/stable/c/d9cb951d11a4ace4de5c50b1178ad211de17079e
https://git.kernel.org/stable/c/4cd66a8016b872a153bf892fe4258cbc0dacf5b1
https://git.kernel.org/stable/c/6369dda4a2209142ab819f01d3d2076d81e3ebdd
https://git.kernel.org/stable/c/9f5495a5c51c1d11c6ffc13aa2befffec0c2651a
https://git.kernel.org/stable/c/a36e506711548df923ceb7ec9f6001375be799a5
reply other threads:[~2025-02-26 2:15 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=2025022606-CVE-2022-49495-7aba@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.