CVE-2024-58084

Source
https://cve.org/CVERecord?id=CVE-2024-58084
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-58084.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2024-58084
Downstream
Related
Published
2025-03-06T16:22:31.998Z
Modified
2026-03-09T23:50:35.007254Z
Severity
  • 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()
Details

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

Database specific
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/58xxx/CVE-2024-58084.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
449d0d84bcd8246b508d07995326d13c54488b8c
Fixed
fee921e3c641f64185abee83f9a6e65f0b380682
Fixed
e03db7c1255ebabba5e1a447754faeb138de15a2
Fixed
b628510397b5cafa1f5d3e848a28affd1c635302

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-58084.json"