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.

Metrics

No CVSS v4.0

Attack Vector Local

Attack Complexity Low

Privileges Required Low

Scope Unchanged

Confidentiality Impact None

Integrity Impact None

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

Exploitation none

Automatable no

Technical Impact partial

Affected Vendors & Products

Vendors Products
Linux
  • Linux Kernel

Configuration 1 [-]

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

No data.

References
Link Providers
https://git.kernel.org/stable/c/b628510397b5cafa1f5d3e848a28affd1c635302 cve-icon cve-icon
https://git.kernel.org/stable/c/e03db7c1255ebabba5e1a447754faeb138de15a2 cve-icon cve-icon
https://git.kernel.org/stable/c/fee921e3c641f64185abee83f9a6e65f0b380682 cve-icon cve-icon
https://lore.kernel.org/linux-cve-announce/2025030634-CVE-2024-58084-16e9@gregkh/T cve-icon
https://nvd.nist.gov/vuln/detail/CVE-2024-58084 cve-icon
https://www.cve.org/CVERecord?id=CVE-2024-58084 cve-icon
History

Thu, 02 Oct 2025 09:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Mon, 24 Mar 2025 18:45:00 +0000

Type Values Removed Values Added
First Time appeared Linux
Linux linux Kernel
Weaknesses CWE-476
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel

Wed, 12 Mar 2025 06:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-20

Fri, 07 Mar 2025 14:00:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

 cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low

Thu, 06 Mar 2025 16:45:00 +0000

Type Values Removed Values Added
Description 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.
Title firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()
References
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published: 2025-03-06T16:22:31.998Z

Updated: 2025-10-01T19:36:35.655Z

Reserved: 2025-03-06T15:52:09.184Z

Link: CVE-2024-58084

cve-icon Vulnrichment

Updated: 2025-10-01T16:57:47.183Z

cve-icon NVD

Status : Modified

Published: 2025-03-06T17:15:21.890

Modified: 2025-10-01T20:18:14.117

Link: CVE-2024-58084

cve-icon Redhat

Severity : Low

Publid Date: 2025-03-06T00:00:00Z

Links: CVE-2024-58084 - Bugzilla