CVE-2022-50239
cpufreq: qcom: fix writes in read-only memory region
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: cpufreq: qcom: fix writes in read-only memory region This commit fixes a kernel oops because of a write in some read-only memory: [ 9.068287] Unable to handle kernel write to read-only memory at virtual address ffff800009240ad8 ..snip.. [ 9.138790] Internal error: Oops: 9600004f [#1] PREEMPT SMP ..snip.. [ 9.269161] Call trace: [ 9.276271] __memcpy+0x5c/0x230 [ 9.278531] snprintf+0x58/0x80 [ 9.282002] qcom_cpufreq_msm8939_name_version+0xb4/0x190 [ 9.284869] qcom_cpufreq_probe+0xc8/0x39c ..snip.. The following line defines a pointer that point to a char buffer stored in read-only memory: char *pvs_name = "speedXX-pvsXX-vXX"; This pointer is meant to hold a template "speedXX-pvsXX-vXX" where the XX values get overridden by the qcom_cpufreq_krait_name_version function. Since the template is actually stored in read-only memory, when the function executes the following call we get an oops: snprintf(*pvs_name, sizeof("speedXX-pvsXX-vXX"), "speed%d-pvs%d-v%d", speed, pvs, pvs_ver); To fix this issue, we instead store the template name onto the stack by using the following syntax: char pvs_name_buffer[] = "speedXX-pvsXX-vXX"; Because the `pvs_name` needs to be able to be assigned to NULL, the template buffer is stored in the pvs_name_buffer and not under the pvs_name variable.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 94% of all CVEs (6 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: High 7.1.
Weakness
Affected products
- affected a8811ec764f95a04ba82f6f457e28c5e9e36e36b – < 794ded0bc461287a268bed21fea2eebb6e5d232c
- affected a8811ec764f95a04ba82f6f457e28c5e9e36e36b – < 14d260f94ff89543597ffea13db8b277a810e08e
- affected a8811ec764f95a04ba82f6f457e28c5e9e36e36b – < b74ee4e301ca01e431e240c046173332966e2431
- affected a8811ec764f95a04ba82f6f457e28c5e9e36e36b – < 01039fb8e90c9cb684430414bff70cea9eb168c5
- affected 5.7
- unaffected < 5.7
- unaffected 5.10.152 – ≤ 5.10.*
- unaffected 5.15.76 – ≤ 5.15.*
- unaffected 6.0.6 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References (4)
- https://git.kernel.org/stable/c/794ded0bc461287a268bed21fea2eebb6e5d232c (opens in a new tab)
- https://git.kernel.org/stable/c/14d260f94ff89543597ffea13db8b277a810e08e (opens in a new tab)
- https://git.kernel.org/stable/c/b74ee4e301ca01e431e240c046173332966e2431 (opens in a new tab)
- https://git.kernel.org/stable/c/01039fb8e90c9cb684430414bff70cea9eb168c5 (opens in a new tab)
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)
- 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://trackcve.app/cve/CVE-2022-50239)Record last updated .