Skip to content
Fencer Vulns
medium 5.5

CVE-2024-58084 json

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

published 2025-03-06 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-54015

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

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.

Patch / fix

  • Linux Linux 6.12.14, 6.13.3, 6.14
  • linux Debian 14, Debian 13 6.12.15-1

debian advisories DEBIAN-CVE-2024-58084

  • linux-gcp-6.11 Ubuntu 24.04 LTS 6.11.0-1015.15~24.04.1
  • linux-hwe-6.11 Ubuntu 24.04 LTS 6.11.0-26.26~24.04.1
  • linux-oem-6.11 Ubuntu 24.04 LTS 6.11.0-1022.22
  • linux-azure-6.11 Ubuntu 24.04 LTS 6.11.0-1015.15~24.04.1
  • linux-nvidia-6.11 Ubuntu 24.04 LTS 6.11.0-1010.10
  • linux-lowlatency-hwe-6.11 Ubuntu 24.04 LTS 6.11.0-1014.15~24.04.1

ubuntu advisories UBUNTU-CVE-2024-58084

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-58084 updated cvss 5.5

kernel: firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool()

  • Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
13 mo ago

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.