From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49485: drm/v3d: Fix null pointer dereference of pointer perfmon
Date: Wed, 26 Feb 2025 03:12:39 +0100 [thread overview]
Message-ID: <2025022605-CVE-2022-49485-a8ec@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/v3d: Fix null pointer dereference of pointer perfmon
In the unlikely event that pointer perfmon is null the WARN_ON return path
occurs after the pointer has already been deferenced. Fix this by only
dereferencing perfmon after it has been null checked.
The Linux kernel CVE team has assigned CVE-2022-49485 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15 with commit 26a4dc29b74a137f45665089f6d3d633fcc9b662 and fixed in 5.15.46 with commit 4be045434923e549a50846a066a04b7b6c1d6d33
Issue introduced in 5.15 with commit 26a4dc29b74a137f45665089f6d3d633fcc9b662 and fixed in 5.17.14 with commit 1df8f8901babcc8c8eea2c067179e455b5c828fd
Issue introduced in 5.15 with commit 26a4dc29b74a137f45665089f6d3d633fcc9b662 and fixed in 5.18.3 with commit 3b72deb784a7d4ae8519a5c584cd87c4b57aa6c8
Issue introduced in 5.15 with commit 26a4dc29b74a137f45665089f6d3d633fcc9b662 and fixed in 5.19 with commit ce7a1ecf3f9f1fccaf67295307614511d8e11b13
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-49485
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/v3d/v3d_perfmon.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/4be045434923e549a50846a066a04b7b6c1d6d33
https://git.kernel.org/stable/c/1df8f8901babcc8c8eea2c067179e455b5c828fd
https://git.kernel.org/stable/c/3b72deb784a7d4ae8519a5c584cd87c4b57aa6c8
https://git.kernel.org/stable/c/ce7a1ecf3f9f1fccaf67295307614511d8e11b13
reply other threads:[~2025-02-26 2:14 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=2025022605-CVE-2022-49485-a8ec@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.