{"uuid": "0824fddd-9046-4e3f-855c-acf9aeb0372c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-58084", "type": "seen", "source": "https://t.me/cvedetector/19731", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-58084 - Qualcomm QCOM Firmware Read Barrier Vulnerability (Data Corruption)\", \n  \"Content\": \"CVE ID : CVE-2024-58084 \nPublished : March 6, 2025, 5:15 p.m. | 1\u00a0hour ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nfirmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()  \n  \nCommit 2e4955167ec5 (\"firmware: qcom: scm: Fix __scm and waitq  \ncompletion variable initialization\") introduced a write barrier in probe  \nfunction to store global '__scm' variable.  We all known barriers are  \npaired (see memory-barriers.txt: \"Note that write barriers should  \nnormally be paired with read or address-dependency barriers\"), therefore  \naccessing it from concurrent contexts requires read barrier.  Previous  \ncommit added such barrier in qcom_scm_is_available(), so let's use that  \ndirectly.  \n  \nLack of this read barrier can result in fetching stale '__scm' variable  \nvalue, NULL, and dereferencing it.  \n  \nNote that barrier in qcom_scm_is_available() satisfies here the control  \ndependency. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-06T19:41:54.000000Z"}