CVE-2022-50239

published 15 Sep 2025 · updated 7 Nov 2026

cpufreq: qcom: fix writes in read-only memory region

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.15.76, Kernel 6.0.6, Kernel 5.10.152 and 4 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=5.11 <5.15.76, >=5.16 <6.0.6, >=5.7 <5.10.152, =6.1, >=a8811ec764f95a04ba82f6f457e28c5e9e36e36b <14d260f94ff89543597ffea13db8b277a810e08e, >=a8811ec764f95a04ba82f6f457e28c5e9e36e36b <794ded0bc461287a268bed21fea2eebb6e5d232c, >=a8811ec764f95a04ba82f6f457e28c5e9e36e36b <b74ee4e301ca01e431e240c046173332966e2431, =5.7, >=a8811ec764f95a04ba82f6f457e28c5e9e36e36b <01039fb8e90c9cb684430414bff70cea9eb168c55.15.76, 6.0.6, 5.10.152, 14d260f94ff89543597ffea13db8b277a810e08e, 794ded0bc461287a268bed21fea2eebb6e5d232c, b74ee4e301ca01e431e240c046173332966e2431, 01039fb8e90c9cb684430414bff70cea9eb168c5
linux-kernel: Kernel>=5.11.0 <5.15.76, >=5.16.0 <6.0.6, >=5.7.0 <5.10.1525.15.76, 6.0.6, 5.10.152

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-50239 severity on Zeptric[![CVE-2022-50239](https://zeptric.io/badge/cve/CVE-2022-50239.svg)](https://zeptric.io/cve/CVE-2022-50239)