{"id":"CVE-2022-50239","title":"cpufreq: qcom: fix writes in read-only memory region","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: qcom: fix writes in read-only memory region\n\nThis commit fixes a kernel oops because of a write in some read-only memory:\n\n\t[    9.068287] Unable to handle ker…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= a8811ec764f95a04ba82f6f457e28c5e9e36e36b < 794ded0bc461287a268bed21fea2eebb6e5d232c","Linux >= a8811ec764f95a04ba82f6f457e28c5e9e36e36b < 14d260f94ff89543597ffea13db8b277a810e08e","Linux >= a8811ec764f95a04ba82f6f457e28c5e9e36e36b < b74ee4e301ca01e431e240c046173332966e2431","Linux >= a8811ec764f95a04ba82f6f457e28c5e9e36e36b < 01039fb8e90c9cb684430414bff70cea9eb168c5","Linux 5.7"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-11-05T20:07:35.394692Z"},"published":"2025-09-15","updated":"2026-11-05","sourceUpdated":"2026-11-05T20:10:30.383Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2022-50239","references":[{"url":"https://git.kernel.org/stable/c/794ded0bc461287a268bed21fea2eebb6e5d232c"},{"url":"https://git.kernel.org/stable/c/14d260f94ff89543597ffea13db8b277a810e08e"},{"url":"https://git.kernel.org/stable/c/b74ee4e301ca01e431e240c046173332966e2431"},{"url":"https://git.kernel.org/stable/c/01039fb8e90c9cb684430414bff70cea9eb168c5"}],"tags":["cve.org"],"epss":0.00163,"epssPercentile":0.05511,"ingestedAt":"2026-11-05T22:38:31.709Z","slug":"CVE-2022-50239","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: qcom: fix writes in read-only memory region\n\nThis commit fixes a kernel oops because of a write in some read-only memory:\n\n\t[    9.068287] Unable to handle kernel write to read-only memory at virtual address ffff800009240ad8\n\t..snip..\n\t[    9.138790] Internal error: Oops: 9600004f [#1] PREEMPT SMP\n\t..snip..\n\t[    9.269161] Call trace:\n\t[    9.276271]  __memcpy+0x5c/0x230\n\t[    9.278531]  snprintf+0x58/0x80\n\t[    9.282002]  qcom_cpufreq_msm8939_name_version+0xb4/0x190\n\t[    9.284869]  qcom_cpufreq_probe+0xc8/0x39c\n\t..snip..\n\nThe following line defines a pointer that point to a char buffer stored\nin read-only memory:\n\n\tchar *pvs_name = \"speedXX-pvsXX-vXX\";\n\nThis pointer is meant to hold a template \"speedXX-pvsXX-vXX\" where the\nXX values get overridden by the qcom_cpufreq_krait_name_version function. Since\nthe template is actually stored in read-only memory, when the function\nexecutes the following call we get an oops:\n\n\tsnprintf(*pvs_name, sizeof(\"speedXX-pvsXX-vXX\"), \"speed%d-pvs%d-v%d\",\n\t\t speed, pvs, pvs_ver);\n\nTo fix this issue, we instead store the template name onto the stack by\nusing the following syntax:\n\n\tchar pvs_name_buffer[] = \"speedXX-pvsXX-vXX\";\n\nBecause the `pvs_name` needs to be able to be assigned to NULL, the\ntemplate buffer is stored in the pvs_name_buffer and not under the\npvs_name variable.\n\n## Affected\n\n- `Linux >= a8811ec764f95a04ba82f6f457e28c5e9e36e36b < 794ded0bc461287a268bed21fea2eebb6e5d232c`\n- `Linux >= a8811ec764f95a04ba82f6f457e28c5e9e36e36b < 14d260f94ff89543597ffea13db8b277a810e08e`\n- `Linux >= a8811ec764f95a04ba82f6f457e28c5e9e36e36b < b74ee4e301ca01e431e240c046173332966e2431`\n- `Linux >= a8811ec764f95a04ba82f6f457e28c5e9e36e36b < 01039fb8e90c9cb684430414bff70cea9eb168c5`\n- `Linux 5.7`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}