CVE-2021-47187
published 2024-04-10CVE-2021-47187: In the Linux kernel, the following vulnerability has been resolved: arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency The entry/exit…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.22%
13.2th percentile
In the Linux kernel, the following vulnerability has been resolved:
arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency
The entry/exit latency and minimum residency in state for the idle
states of MSM8998 were ..bad: first of all, for all of them the
timings were written for CPU sleep but the min-residency-us param
was miscalculated (supposedly, while porting this from downstream);
Then, the power collapse states are setting PC on both the CPU
cluster *and* the L2 cache, which have different timings: in the
specific case of L2 the times are higher so these ones should be
taken into account instead of the CPU ones.
This parameter misconfiguration was not giving particular issues
because on MSM8998 there was no CPU scaling at all, so cluster/L2
power collapse was rarely (if ever) hit.
When CPU scaling is enabled, though, the wrong timings will produce
SoC unstability shown to the user as random, apparently error-less,
sudden reboots and/or lockups.
This set of parameters are stabilizing the SoC when CPU scaling is
ON and when power collapse is frequently hit.
Affected
13 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.15.5-1 (bookworm) | linux 5.15.5-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= c3083c80b52c4e29b65ed838d2e66a91b13a3152 < a14d7038ea201c5526375becfc43b9ba281b1e82 | a14d7038ea201c5526375becfc43b9ba281b1e82 |
| linux | linux | >= c3083c80b52c4e29b65ed838d2e66a91b13a3152 < e52fecdd0c142b95c720683885b06ee3f0e065c8 | e52fecdd0c142b95c720683885b06ee3f0e065c8 |
| linux | linux | >= c3083c80b52c4e29b65ed838d2e66a91b13a3152 < 118c826ef8b43efe0fda8faf419673707ee8c5e5 | 118c826ef8b43efe0fda8faf419673707ee8c5e5 |
| linux | linux | >= c3083c80b52c4e29b65ed838d2e66a91b13a3152 < 3f1dcaff642e75c1d2ad03f783fa8a3b1f56dd50 | 3f1dcaff642e75c1d2ad03f783fa8a3b1f56dd50 |
| linux | linux_kernel | < 5.4.162 | 5.4.162 |
| linux | linux_kernel | >= 0 < 5.10.84-1 | 5.10.84-1 |
| linux | linux_kernel | >= 0 < 5.15.5-1 | 5.15.5-1 |
| linux | linux_kernel | >= 0 < 5.15.5-1 | 5.15.5-1 |
| linux | linux_kernel | >= 0 < 5.15.5-1 | 5.15.5-1 |
| linux | linux_kernel | >= 5.11 < 5.15.5 | 5.15.5 |
| linux | linux_kernel | >= 5.5 < 5.10.82 | 5.10.82 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-28cr-jmcx-rqcp: In the Linux kernel, the following vulnerability has been resolved:
arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency
The entry
ghsa_unreviewed·2024-04-10
CVE-2021-47187 [MEDIUM] GHSA-28cr-jmcx-rqcp: In the Linux kernel, the following vulnerability has been resolved:
arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency
The entry
In the Linux kernel, the following vulnerability has been resolved:
arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency
The entry/exit latency and minimum residency in state for the idle
states of MSM8998 were ..bad: first of all, for all of them the
timings were written for CPU sleep but the min-residency-us param
was miscalculated (supposedly, while porting this from downstream);
Then, the power collapse states are setting PC on both the CPU
cluster *and* the L2 cache, which have different timings: in the
specific case of L2 the times are higher so these ones should be
taken into account instead of the CPU ones.
This parameter misconfiguration was not giving particular issues
because on MSM8998 there was no CPU scaling at all, so cluster/L2
power collapse was rarely
OSV
CVE-2021-47187: In the Linux kernel, the following vulnerability has been resolved: arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency The entry/e
osv·2024-04-10·CVSS 5.5
CVE-2021-47187 [MEDIUM] CVE-2021-47187: In the Linux kernel, the following vulnerability has been resolved: arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency The entry/e
In the Linux kernel, the following vulnerability has been resolved: arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency The entry/exit latency and minimum residency in state for the idle states of MSM8998 were ..bad: first of all, for all of them the timings were written for CPU sleep but the min-residency-us param was miscalculated (supposedly, while porting this from downstream); Then, the power collapse states are setting PC on both the CPU cluster *and* the L2 cache, which have different timings: in the specific case of L2 the times are higher so these ones should be taken into account instead of the CPU ones. This parameter misconfiguration was not giving particular issues because on MSM8998 there was no CPU scaling at all, so cluster/L2 power collapse was rarely (i
Red Hat
kernel: arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency
vendor_redhat·2024-04-10·CVSS 5.5
CVE-2021-47187 [MEDIUM] CWE-1176 kernel: arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency
kernel: arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency
In the Linux kernel, the following vulnerability has been resolved:
arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency
The entry/exit latency and minimum residency in state for the idle
states of MSM8998 were ..bad: first of all, for all of them the
timings were written for CPU sleep but the min-residency-us param
was miscalculated (supposedly, while porting this from downstream);
Then, the power collapse states are setting PC on both the CPU
cluster *and* the L2 cache, which have different timings: in the
specific case of L2 the times are higher so these ones should be
taken into account instead of the CPU ones.
This parameter misconfiguration was not giving particular issues
because on MSM
Debian
CVE-2021-47187: linux - In the Linux kernel, the following vulnerability has been resolved: arm64: dts:...
vendor_debian·2021·CVSS 5.5
CVE-2021-47187 [MEDIUM] CVE-2021-47187: linux - In the Linux kernel, the following vulnerability has been resolved: arm64: dts:...
In the Linux kernel, the following vulnerability has been resolved: arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency The entry/exit latency and minimum residency in state for the idle states of MSM8998 were ..bad: first of all, for all of them the timings were written for CPU sleep but the min-residency-us param was miscalculated (supposedly, while porting this from downstream); Then, the power collapse states are setting PC on both the CPU cluster *and* the L2 cache, which have different timings: in the specific case of L2 the times are higher so these ones should be taken into account instead of the CPU ones. This parameter misconfiguration was not giving particular issues because on MSM8998 there was no CPU scaling at all, so cluster/L2 power collapse was rarely (i
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/118c826ef8b43efe0fda8faf419673707ee8c5e5https://git.kernel.org/stable/c/3f1dcaff642e75c1d2ad03f783fa8a3b1f56dd50https://git.kernel.org/stable/c/a14d7038ea201c5526375becfc43b9ba281b1e82https://git.kernel.org/stable/c/e52fecdd0c142b95c720683885b06ee3f0e065c8https://git.kernel.org/stable/c/118c826ef8b43efe0fda8faf419673707ee8c5e5https://git.kernel.org/stable/c/3f1dcaff642e75c1d2ad03f783fa8a3b1f56dd50https://git.kernel.org/stable/c/a14d7038ea201c5526375becfc43b9ba281b1e82https://git.kernel.org/stable/c/e52fecdd0c142b95c720683885b06ee3f0e065c8
2024-04-10
Published