4.3
CVE-2025-0932
- EPSS 0.04%
- Veröffentlicht 04.08.2025 10:15:27
- Zuletzt bearbeitet 05.08.2025 19:15:31
- Quelle arm-security@arm.com
- Teams Watchlist Login
- Unerledigt Login
Use After Free vulnerability in Arm Ltd Bifrost GPU Userspace Driver, Arm Ltd Valhall GPU Userspace Driver, Arm Ltd Arm 5th Gen GPU Architecture Userspace Driver allows a non-privileged user process to perform valid GPU processing operations, including via WebGL or WebGPU, to gain access to already freed memory.This issue affects Bifrost GPU Userspace Driver: from r48p0 through r49p3, from r50p0 through r51p0; Valhall GPU Userspace Driver: from r48p0 through r49p3, from r50p0 through r54p0; Arm 5th Gen GPU Architecture Userspace Driver: from r48p0 through r49p3, from r50p0 through r54p0.
Verknüpft mit AI von unstrukturierten Daten zu bestehenden CPE der NVD
Diese Information steht angemeldeten Benutzern zur Verfügung. Login
Daten sind bereitgestellt durch das CVE Programm von einer CVE Numbering Authority (CNA) (Unstrukturiert).
HerstellerArm Ltd
≫
Produkt
Bifrost GPU Userspace Driver
Default Statusunaffected
Version <=
r49p3
Version
r48p0
Status
affected
Version <=
r51p0
Version
r50p0
Status
affected
HerstellerArm Ltd
≫
Produkt
Valhall GPU Userspace Driver
Default Statusunaffected
Version <=
r49p3
Version
r48p0
Status
affected
Version <=
r54p0
Version
r50p0
Status
affected
HerstellerArm Ltd
≫
Produkt
Arm 5th Gen GPU Architecture Userspace Driver
Default Statusunaffected
Version <=
r49p3
Version
r48p0
Status
affected
Version <=
r54p0
Version
r50p0
Status
affected
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
| Typ | Quelle | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.04% | 0.086 |
| Quelle | Base Score | Exploit Score | Impact Score | Vector String |
|---|---|---|---|---|
| 134c704f-9b21-4f2e-91b3-4a467353bcc0 | 4.3 | 2.8 | 1.4 |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
|
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.