From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49106: staging: vchiq_arm: Avoid NULL ptr deref in vchiq_dump_platform_instances
Date: Wed, 26 Feb 2025 02:55:11 +0100 [thread overview]
Message-ID: <2025022601-CVE-2022-49106-7fa5@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
staging: vchiq_arm: Avoid NULL ptr deref in vchiq_dump_platform_instances
vchiq_get_state() can return a NULL pointer. So handle this cases and
avoid a NULL pointer derefence in vchiq_dump_platform_instances.
The Linux kernel CVE team has assigned CVE-2022-49106 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.34 with commit 176df12b38c70b0a45e6392a0ee5bc83489dfc29
Fixed in 5.16.20 with commit 4627250cabaa80278d3ab01ad107893cea83799f
Fixed in 5.17.3 with commit 51e5e5c34c22c0bfec0808d8c33e0b2fcf4c7c89
Fixed in 5.18 with commit aa899e686d442c63d50f4d369cc02dbbf0941cb0
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-49106
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/staging/vc04_services/interface/vchiq_arm/vchiq_arm.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/176df12b38c70b0a45e6392a0ee5bc83489dfc29
https://git.kernel.org/stable/c/4627250cabaa80278d3ab01ad107893cea83799f
https://git.kernel.org/stable/c/51e5e5c34c22c0bfec0808d8c33e0b2fcf4c7c89
https://git.kernel.org/stable/c/aa899e686d442c63d50f4d369cc02dbbf0941cb0
reply other threads:[~2025-02-26 1:58 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=2025022601-CVE-2022-49106-7fa5@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.