CVE-2021-47187arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency
- 5.5MediumCVSS base score
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 16 days later
· 16 days later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected c3083c80b52c4e29b65ed838d2e66a91b13a3152 – < a14d7038ea201c5526375becfc43b9ba281b1e82
- affected c3083c80b52c4e29b65ed838d2e66a91b13a3152 – < e52fecdd0c142b95c720683885b06ee3f0e065c8
- affected c3083c80b52c4e29b65ed838d2e66a91b13a3152 – < 118c826ef8b43efe0fda8faf419673707ee8c5e5
- affected c3083c80b52c4e29b65ed838d2e66a91b13a3152 – < 3f1dcaff642e75c1d2ad03f783fa8a3b1f56dd50
- affected 5.3
- unaffected < 5.3
- unaffected 5.4.162 – ≤ 5.4.*
- unaffected 5.10.82 – ≤ 5.10.*
- unaffected 5.15.5 – ≤ 5.15.*
- unaffected 5.16 – ≤ *
References
References4
- https://git.kernel.org/stable/c/a14d7038ea201c5526375becfc43b9ba281b1e82 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/e52fecdd0c142b95c720683885b06ee3f0e065c8 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/118c826ef8b43efe0fda8faf419673707ee8c5e5 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/3f1dcaff642e75c1d2ad03f783fa8a3b1f56dd50 (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2021-33835 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2021-47187)Record last updated .