5.3
CVE-2025-3212
- EPSS 0.05%
- Published 08.09.2025 12:53:44
- Last modified 08.09.2025 20:15:34
- Source arm-security@arm.com
- Teams watchlist Login
- Open Login
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.
Verknüpft mit AI von unstrukturierten Daten zu bestehenden CPE der NVD
This information is available to logged-in users. Login
Daten sind bereitgestellt durch das CVE Programm von einer CVE Numbering Authority (CNA) (Unstrukturiert).
VendorArm Ltd
≫
Product
Bifrost GPU Kernel Driver
Default Statusunaffected
Version <=
r49p4
Version
r41p0
Status
affected
Version <=
r51p0
Version
r50p0
Status
affected
VendorArm Ltd
≫
Product
Valhall GPU Kernel Driver
Default Statusunaffected
Version <=
r49p4
Version
r41p0
Status
affected
Version <=
r54p0
Version
r50p0
Status
affected
VendorArm Ltd
≫
Product
Arm 5th Gen GPU Architecture Kernel Driver
Default Statusunaffected
Version <=
r49p4
Version
r41p0
Status
affected
Version <=
r54p0
Version
r50p0
Status
affected
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Type | Source | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 0.05% | 0.156 |
Source | Base Score | Exploit Score | Impact Score | Vector string |
---|---|---|---|---|
134c704f-9b21-4f2e-91b3-4a467353bcc0 | 5.3 | 3.9 | 1.4 |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
|
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.