Linux Kernel up to 6.12.13/6.13.2 qcom_scm_get_tzmem_pool initialization

Summaryinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.12.13/6.13.2. Affected by this issue is the function qcom_scm_get_tzmem_pool. The manipulation results in initialization. This vulnerability is known as CVE-2024-58084. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.13/6.13.2. It has been classified as critical. Affected is the function qcom_scm_get_tzmem_pool. The manipulation with an unknown input leads to a initialization vulnerability. CWE is classifying the issue as CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2024-58084 since 03/06/2025. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 02/16/2026).

The vulnerability scanner Nessus provides a plugin with the ID 232241 (Linux Distros Unpatched Vulnerability : CVE-2024-58084), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.12.14, 6.13.3 or 6.14-rc1 eliminates this vulnerability. Applying the patch fee921e3c641f64185abee83f9a6e65f0b380682/e03db7c1255ebabba5e1a447754faeb138de15a2/b628510397b5cafa1f5d3e848a28affd1c635302 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (232241) and CERT Bund (WID-SEC-2025-0499). Once again VulDB remains the best source for vulnerability data.

Affected

• Google Container-Optimized OS
• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• Oracle Linux
• RESF Rocky Linux
• SolarWinds Security Event Manager
• Open Source Linux Kernel
• Dell Secure Connect Gateway

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.12.0
• 6.12.1
• 6.12.2
• 6.12.3
• 6.12.4
• 6.12.5
• 6.12.6
• 6.12.7
• 6.12.8
• 6.12.9
• 6.12.10
• 6.12.11
• 6.12.12
• 6.12.13
• 6.13.0
• 6.13.1
• 6.13.2

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion