From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-22011: ARM: dts: bcm2711: Fix xHCI power-domain
Date: Tue, 8 Apr 2025 10:16:45 +0200 [thread overview]
Message-ID: <2025040843-CVE-2025-22011-9e83@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ARM: dts: bcm2711: Fix xHCI power-domain
During s2idle tests on the Raspberry CM4 the VPU firmware always crashes
on xHCI power-domain resume:
root@raspberrypi:/sys/power# echo freeze > state
[ 70.724347] xhci_suspend finished
[ 70.727730] xhci_plat_suspend finished
[ 70.755624] bcm2835-power bcm2835-power: Power grafx off
[ 70.761127] USB: Set power to 0
[ 74.653040] USB: Failed to set power to 1 (-110)
This seems to be caused because of the mixed usage of
raspberrypi-power and bcm2835-power at the same time. So avoid
the usage of the VPU firmware power-domain driver, which
prevents the VPU crash.
The Linux kernel CVE team has assigned CVE-2025-22011 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.8 with commit 522c35e08b53f157ad3e51848caa861b258001e4 and fixed in 6.12.21 with commit b8a47aa0b3df701d0fc41b3caf78d00571776be0
Issue introduced in 6.8 with commit 522c35e08b53f157ad3e51848caa861b258001e4 and fixed in 6.13.9 with commit 393947e06867923d4c2be380d46efd03407a8ce2
Issue introduced in 6.8 with commit 522c35e08b53f157ad3e51848caa861b258001e4 and fixed in 6.14 with commit f44fa354a0715577ca32b085f6f60bcf32c748dd
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-2025-22011
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:
arch/arm/boot/dts/broadcom/bcm2711-rpi.dtsi
arch/arm/boot/dts/broadcom/bcm2711.dtsi
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/b8a47aa0b3df701d0fc41b3caf78d00571776be0
https://git.kernel.org/stable/c/393947e06867923d4c2be380d46efd03407a8ce2
https://git.kernel.org/stable/c/f44fa354a0715577ca32b085f6f60bcf32c748dd
reply other threads:[~2025-04-08 8:18 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=2025040843-CVE-2025-22011-9e83@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.