CVE-2022-50239: cpufreq: qcom: fix writes in read-only memory region

Q: What is the severity of CVE-2022-50239?

CVE-2022-50239 has been categorized with a high severity due to its potential impact on system stability.

Q: How do I fix CVE-2022-50239?

To fix CVE-2022-50239, you should update your Linux kernel to the latest version where this vulnerability has been resolved.

Q: What are the implications of CVE-2022-50239?

The implications of CVE-2022-50239 include potential kernel crashes and unstable system behavior caused by improper memory writes.

Q: Which Linux kernel versions are affected by CVE-2022-50239?

CVE-2022-50239 affects multiple versions of the Linux kernel prior to the fix being implemented.

Q: Is CVE-2022-50239 actively exploited in the wild?

As of now, there is no reported evidence that CVE-2022-50239 is being actively exploited in the wild.

Published Sep 15, 2025

Updated

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] qcomcpufreqmsm8939nameversion+0xb4/0x190 [ 9.284869] qcomcpufreqprobe+0xc8/0x39c ..snip..

The following line defines a pointer that point to a char buffer stored in read-only memory:

char pvsname = "speedXX-pvsXX-vXX";

This pointer is meant to hold a template "speedXX-pvsXX-vXX" where the XX values get overridden by the qcomcpufreqkraitnameversion function. Since the template is actually stored in read-only memory, when the function executes the following call we get an oops:

snprintf(pvsname, sizeof("speedXX-pvsXX-vXX"), "speed%d-pvs%d-v%d", speed, pvs, pvsver);

To fix this issue, we instead store the template name onto the stack by using the following syntax:

char pvsnamebuffer[] = "speedXX-pvsXX-vXX";

Because the pvsname needs to be able to be assigned to NULL, the template buffer is stored in the pvsnamebuffer and not under the pvsname variable.

Affected Software

122 affected componentsFixes available

Linux Foundation Linux Kernel

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-aws-5.15<5.15.0-1030.34~20.04.1

5.15.0-1030.34~20.04.1

ubuntu/linux-azure-5.15<5.15.0-1033.40~20.04.1

5.15.0-1033.40~20.04.1

ubuntu/linux-gcp-5.15<5.15.0-1029.36~20.04.1

5.15.0-1029.36~20.04.1

ubuntu/linux-hwe-5.15<5.15.0-60.66~20.04.1

5.15.0-60.66~20.04.1

ubuntu/linux-intel-iotg-5.15<5.15.0-1025.30~20.04.1

5.15.0-1025.30~20.04.1

ubuntu/linux-lowlatency-hwe-5.15<5.15.0-60.66~20.04.1

5.15.0-60.66~20.04.1

ubuntu/linux-oracle-5.15<5.15.0-1029.35~20.04.1

5.15.0-1029.35~20.04.1

ubuntu/linux-riscv-5.15<5.15.0-1029.33~20.04.1

5.15.0-1029.33~20.04.1

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.8*

ubuntu/linux-intel-5.13*

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux<5.15.0-60.66

5.15.0-60.66

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws<5.15.0-1030.34

5.15.0-1030.34

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-azure<5.15.0-1033.40

5.15.0-1033.40

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-fde<5.15.0-1033.40.1

5.15.0-1033.40.1

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-gcp<5.15.0-1029.36

5.15.0-1029.36

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-gke<5.15.0-1027.32

5.15.0-1027.32

ubuntu/linux-gkeop<5.15.0-1015.19

5.15.0-1015.19

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-ibm<5.15.0-1025.28

5.15.0-1025.28

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-intel-iotg<5.15.0-1025.30

5.15.0-1025.30

ubuntu/linux-kvm<5.15.0-1028.33

5.15.0-1028.33

ubuntu/linux-lowlatency<5.15.0-60.66

5.15.0-60.66

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-nvidia<5.15.0-1017.17

5.15.0-1017.17

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle<5.15.0-1029.35

5.15.0-1029.35

ubuntu/linux-oracle-6.5*

ubuntu/linux-raspi<5.15.0-1024.26

5.15.0-1024.26

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-bluefield<5.15.0-1014.16

5.15.0-1014.16

ubuntu/linux-azure-6.11*

ubuntu/linux-gcp-6.11*

ubuntu/linux-hwe-6.11*

ubuntu/linux-intel*

ubuntu/linux-lowlatency-hwe-6.11*

ubuntu/linux-oem-6.11*

ubuntu/linux-oem-6.8*

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

Linux Linux kernel>=5.7<5.10.152

Linux Linux kernel>=5.11<5.15.76

Linux Linux kernel>=5.16<6.0.6

Linux Linux kernel=6.1-rc1

debian/linux<6.0.6-1

6.0.6-1

debian/linux<6.0.6-1

6.0.6-1

debian/linux<6.0.6-1

6.0.6-1

linux/kernel>=5.7.0<5.10.152

5.10.152

linux/kernel>=5.11.0<5.15.76

5.15.76

linux/kernel>=5.16.0<6.0.6

6.0.6

debian/linux

6.1.176-16.1.190-16.12.107-16.12.115-27.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1030.34~20.04.1
Upgrade
Upgrade ubuntu/linux-azure-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1033.40~20.04.1
Upgrade
Upgrade ubuntu/linux-gcp-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1029.36~20.04.1
Upgrade
Upgrade ubuntu/linux-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-60.66~20.04.1
Upgrade
Upgrade ubuntu/linux-intel-iotg-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1025.30~20.04.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-60.66~20.04.1
Upgrade
Upgrade ubuntu/linux-oracle-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1029.35~20.04.1
Upgrade
Upgrade ubuntu/linux-riscv-5.15 to a version that resolves this vulnerability.
Fixed in 5.15.0-1029.33~20.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 5.15.0-60.66
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 5.15.0-1030.34
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 5.15.0-1033.40
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 5.15.0-1033.40.1
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 5.15.0-1029.36
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 5.15.0-1027.32
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 5.15.0-1015.19
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 5.15.0-1025.28
Upgrade
Upgrade ubuntu/linux-intel-iotg to a version that resolves this vulnerability.
Fixed in 5.15.0-1025.30
Upgrade
Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.
Fixed in 5.15.0-1028.33
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 5.15.0-60.66
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 5.15.0-1017.17
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 5.15.0-1029.35
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 5.15.0-1024.26
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 5.15.0-1014.16
Upgrade
Upgrade debian/linux to a version that resolves this vulnerability.
Fixed in 6.0.6-1
Upgrade
Upgrade linux/Kernel to a version that resolves this vulnerability.
Fixed in 5.10.152
Upgrade
Upgrade linux/Kernel to a version that resolves this vulnerability.
Fixed in 5.15.76
Upgrade
Upgrade linux/Kernel to a version that resolves this vulnerability.
Fixed in 6.0.6
Upgrade
Upgrade debian/linux to a version that resolves this vulnerability.
Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.15-1

Event History

Sep 15, 2025

CVE Published

via MITRE·02:01 PM

Data Sourced

via MITRE·02:01 PM

Description

Data Sourced

via OSV·02:01 PM

DescriptionAffected Software

Data Sourced

via OSV·02:15 PM

Severity

Data Sourced

via NVD·02:15 PM

RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

What is the severity of CVE-2022-50239?

CVE-2022-50239 has been categorized with a high severity due to its potential impact on system stability.

How do I fix CVE-2022-50239?

To fix CVE-2022-50239, you should update your Linux kernel to the latest version where this vulnerability has been resolved.

What are the implications of CVE-2022-50239?

The implications of CVE-2022-50239 include potential kernel crashes and unstable system behavior caused by improper memory writes.

Which Linux kernel versions are affected by CVE-2022-50239?

CVE-2022-50239 affects multiple versions of the Linux kernel prior to the fix being implemented.

Is CVE-2022-50239 actively exploited in the wild?

As of now, there is no reported evidence that CVE-2022-50239 is being actively exploited in the wild.

CVE-2022-50239: cpufreq: qcom: fix writes in read-only memory region

Affected Software

Remediation

Event History

Frequently Asked Questions

What is the severity of CVE-2022-50239?

How do I fix CVE-2022-50239?

What are the implications of CVE-2022-50239?

Which Linux kernel versions are affected by CVE-2022-50239?

Is CVE-2022-50239 actively exploited in the wild?

Company

Resources

Contact