CVE-2024-58084: firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()

Published Mar 6, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

firmware: qcom: scm: Fix missing read barrier in qcomscmgettzmempool()

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 qcomscmisavailable(), 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 qcomscmisavailable() satisfies here the control dependency.

Affected Software

6 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=6.11<=6.12.14
Linux Linux kernel>=6.13<=6.13.3
debian/linux<6.12.15-1
6.12.15-1
debian/linux<6.12.15-1
6.12.15-1
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.15-1
  2. 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.12-1Fixed in 7.2.15-1
  3. Compensating control

    Use the read barrier in qcom_scm_is_available() directly when accessing the global __scm variable from concurrent contexts, including qcom_scm_get_tzmem_pool().

Event History

Mar 6, 2025
CVE Published
via MITRE·04:22 PM
Data Sourced
via MITRE·04:22 PM
Description
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·05:15 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

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.

2

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.

3

What systems are affected by CVE-2024-58084?

CVE-2024-58084 affects the Linux kernel, particularly those utilizing firmware components related to Qualcomm SCM.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203