CVE-2024-58084 (GCVE-0-2024-58084)
Vulnerability from cvelistv5
Published
2025-03-06 16:22
Modified
2025-05-04 10:09
Severity ?
VLAI Severity ?
EPSS score ?
Summary
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.
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/firmware/qcom/qcom_scm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "fee921e3c641f64185abee83f9a6e65f0b380682",
"status": "affected",
"version": "449d0d84bcd8246b508d07995326d13c54488b8c",
"versionType": "git"
},
{
"lessThan": "e03db7c1255ebabba5e1a447754faeb138de15a2",
"status": "affected",
"version": "449d0d84bcd8246b508d07995326d13c54488b8c",
"versionType": "git"
},
{
"lessThan": "b628510397b5cafa1f5d3e848a28affd1c635302",
"status": "affected",
"version": "449d0d84bcd8246b508d07995326d13c54488b8c",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/firmware/qcom/qcom_scm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.11"
},
{
"lessThan": "6.11",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.14",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.13.*",
"status": "unaffected",
"version": "6.13.3",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.14",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.14",
"versionStartIncluding": "6.11",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.13.3",
"versionStartIncluding": "6.11",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.14",
"versionStartIncluding": "6.11",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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 \u0027__scm\u0027 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\u0027s use that\ndirectly.\n\nLack of this read barrier can result in fetching stale \u0027__scm\u0027 variable\nvalue, NULL, and dereferencing it.\n\nNote that barrier in qcom_scm_is_available() satisfies here the control\ndependency."
}
],
"providerMetadata": {
"dateUpdated": "2025-05-04T10:09:42.783Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/fee921e3c641f64185abee83f9a6e65f0b380682"
},
{
"url": "https://git.kernel.org/stable/c/e03db7c1255ebabba5e1a447754faeb138de15a2"
},
{
"url": "https://git.kernel.org/stable/c/b628510397b5cafa1f5d3e848a28affd1c635302"
}
],
"title": "firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2024-58084",
"datePublished": "2025-03-06T16:22:31.998Z",
"dateReserved": "2025-03-06T15:52:09.184Z",
"dateUpdated": "2025-05-04T10:09:42.783Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"vulnerability-lookup:meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2024-58084\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-03-06T17:15:21.890\",\"lastModified\":\"2025-03-24T18:30:09.320\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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 \u0027__scm\u0027 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\u0027s use that\\ndirectly.\\n\\nLack of this read barrier can result in fetching stale \u0027__scm\u0027 variable\\nvalue, NULL, and dereferencing it.\\n\\nNote that barrier in qcom_scm_is_available() satisfies here the control\\ndependency.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool() el commit 2e4955167ec5 (\\\"firmware: qcom: scm: Fix __scm and waitq ending variable initialization\\\") introdujo una barrera de escritura en la funci\u00f3n de sondeo para almacenar la variable global \u0027__scm\u0027. Todos sabemos que las barreras est\u00e1n emparejadas (consulte memory-barriers.txt: \\\"Note que las barreras de escritura normalmente deben emparejarse con barreras de lectura o de dependencia de direcci\u00f3n\\\"), por lo tanto, acceder a ellas desde contextos concurrentes requiere una barrera de lectura. Una confirmaci\u00f3n anterior agreg\u00f3 dicha barrera en qcom_scm_is_available(), as\u00ed que us\u00e9mosla directamente. La falta de esta barrera de lectura puede resultar en la obtenci\u00f3n del valor de la variable \u0027__scm\u0027 obsoleto, NULL, y su desreferenciaci\u00f3n. Tenga en cuenta que la barrera en qcom_scm_is_available() satisface aqu\u00ed la dependencia de control.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-476\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.11\",\"versionEndIncluding\":\"6.12.14\",\"matchCriteriaId\":\"7C014E1B-02EA-488C-AD8B-52F51437381F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.13\",\"versionEndIncluding\":\"6.13.3\",\"matchCriteriaId\":\"DDB61369-A1FA-42E6-A1FC-78476A6D432A\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/b628510397b5cafa1f5d3e848a28affd1c635302\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/e03db7c1255ebabba5e1a447754faeb138de15a2\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/fee921e3c641f64185abee83f9a6e65f0b380682\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}"
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…