CVE-2024-58084: firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()
First published: Thu Mar 06 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool() Commit 2e4955167ec5 ("firmware: qcom: scm: Fix __scm and waitq completion variable initialization") introduced a write barrier in probe function to store global '__scm' variable. We all known barriers are paired (see memory-barriers.txt: "Note that write barriers should normally be paired with read or address-dependency barriers"), therefore accessing it from concurrent contexts requires read barrier. Previous commit added such barrier in qcom_scm_is_available(), so let's use that directly. Lack of this read barrier can result in fetching stale '__scm' variable value, NULL, and dereferencing it. Note that barrier in qcom_scm_is_available() satisfies here the control dependency.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| Linux Kernel | >=6.11<=6.12.14 | |
| Linux Kernel | >=6.13<=6.13.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-58084?
CVE-2024-58084 has been classified as a vulnerability that could affect system stability and security in the Linux kernel.
How do I fix CVE-2024-58084?
To mitigate CVE-2024-58084, users should update their Linux kernel to the latest version that includes the patch addressing this vulnerability.
What systems are affected by CVE-2024-58084?
CVE-2024-58084 affects the Linux kernel, particularly those utilizing firmware components related to Qualcomm SCM.
Is CVE-2024-58084 a remote exploitation vulnerability?
CVE-2024-58084 is not categorized specifically as a remote exploitation vulnerability, but it may impact system operations.
What are the consequences of not addressing CVE-2024-58084?
Failing to address CVE-2024-58084 could lead to potential instabilities or security risks within systems running the affected Linux kernel.
- agent/title
- agent/references
- agent/first-publish-date
- agent/type
- agent/description
- agent/guess-ai
- agent/software-canonical-lookup
- agent/author
- agent/source
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/remedy
- agent/last-modified-date
- agent/softwarecombine
- agent/event
- agent/tags
- collector/nvd-api
- source/NVD
- vendor/linux
- canonical/linux kernel
- version/linux kernel/6.11
- version/linux kernel/6.12.14
- version/linux kernel/6.13
- version/linux kernel/6.13.3