CVE-2021-47187

arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency

State
Published
Severity
Not scored
Published
Apr 10, 2024
Updated
May 11, 2026
Reserved
Mar 25, 2024

Read the record on cve.org

Description

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • c3083c80b52c4e29b65ed838d2e66a91b13a3152 to before a14d7038ea201c5526375becfc43b9ba281b1e82Affected
  • c3083c80b52c4e29b65ed838d2e66a91b13a3152 to before e52fecdd0c142b95c720683885b06ee3f0e065c8Affected
  • c3083c80b52c4e29b65ed838d2e66a91b13a3152 to before 118c826ef8b43efe0fda8faf419673707ee8c5e5Affected
  • c3083c80b52c4e29b65ed838d2e66a91b13a3152 to before 3f1dcaff642e75c1d2ad03f783fa8a3b1f56dd50Affected
LinuxLinux
  • 5.3Affected
  • before 5.3Not affected
  • 5.4.162 through 5.4.*Not affected
  • 5.10.82 through 5.10.*Not affected
  • 5.15.5 through 5.15.*Not affected
  • 5.16 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.