NULL Pointer Dereference Affecting linux-virt package, versions <6.12.15-r0


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.02% (5th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about NULL Pointer Dereference vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-LINUXVIRT-13307700
  • published6 Oct 2025
  • disclosed6 Mar 2025

Introduced: 6 Mar 2025

CVE-2024-58084  (opens in a new tab)
CWE-476  (opens in a new tab)

How to fix?

Upgrade Minimos:latest linux-virt to version 6.12.15-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream linux-virt package and not the linux-virt package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1