CVE-2025-3212 Vulnerability Analysis & Exploit Details

CVE-2025-3212
Vulnerability Scoring

5.3
/10
Significant Risk

Security assessments indicate that CVE-2025-3212 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-3212 Details

Status: Analyzed

Last updated: 🕞 18 Dec 2025, 15:42 UTC
Originally published on: 🕐 08 Sep 2025, 13:15 UTC

Time between publication and last update: 101 days

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CVE-2025-3212 Vulnerability Summary

CVE-2025-3212: Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform valid GPU memory processing operations to gain access to already freed memory.This issue affects Bifrost GPU Kernel Driver: from r41p0 through r49p4, from r50p0 through r51p0; Valhall GPU Kernel Driver: from r41p0 through r49p4, from r50p0 through r54p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 through r49p4, from r50p0 through r54p0.

Assessing the Risk of CVE-2025-3212

Access Complexity Graph

The exploitability of CVE-2025-3212 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-3212

With low attack complexity and no required privileges, CVE-2025-3212 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-3212, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-3212, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2025-3212 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2025-3212 poses no threat to data integrity.
  • Availability: Low
    CVE-2025-3212 may slightly degrade system performance without fully affecting service availability.

CVE-2025-3212 References

External References

CWE Common Weakness Enumeration

CWE-416

Vulnerable Configurations

  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r41p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r41p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r42p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r42p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r43p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r43p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r44p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r44p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r44p1:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r44p1:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r45p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r45p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r46p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r46p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r47p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r47p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r48p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r48p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r49p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r49p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r49p1:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r49p1:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r49p3:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r49p3:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r49p4:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r49p4:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r50p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r50p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r51p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r51p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r52p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r52p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r53p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r53p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r54p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver:r54p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r41p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r41p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r42p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r42p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r43p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r43p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r44p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r44p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r44p1:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r44p1:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r45p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r45p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r46p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r46p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r47p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r47p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r48p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r48p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r49p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r49p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r49p1:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r49p1:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r49p3:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r49p3:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r49p4:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r49p4:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r50p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r50p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r51p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:bifrost_gpu_kernel_driver:r51p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r41p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r41p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r42p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r42p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r43p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r43p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r44p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r44p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r44p1:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r44p1:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r45p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r45p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r46p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r46p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r47p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r47p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r48p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r48p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r49p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r49p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r49p1:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r49p1:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r49p3:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r49p3:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r49p4:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r49p4:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r50p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r50p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r51p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r51p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r52p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r52p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r53p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r53p0:*:*:*:*:*:*:*
  • cpe:2.3:a:arm:valhall_gpu_kernel_driver:r54p0:*:*:*:*:*:*:*
    cpe:2.3:a:arm:valhall_gpu_kernel_driver:r54p0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-3212: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-68942 – Gitea before 1.22.2 allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text.
  • CVE-2025-68941 – Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources.
  • CVE-2025-68940 – In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request.
  • CVE-2025-68939 – Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API.
  • CVE-2025-15098 – A vulnerability was determined in YunaiV yudao-cloud up to 2025.11. This affects the function BpmHttpCallbackTrigger/BpmSyncHttpRequestTrigger of t...