GPU DDK - UAF read and/or write of arbitrary physical memory due to integer truncation in PMRDevPhysAddrOSMem
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Imagination Technologies | Graphics DDK | unknown |
|
Configuration 1 [-]
| AND |
|
No data.
| Vendor | Product | Versions | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Imaginationtech | Graphics Ddk |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.167% probability within 30 days)
| Link | Providers |
|---|---|
| https://www.imaginationtech.com/gpu-driver-vulnerabilities/ |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google android Imaginationtech ddk Linux Linux linux Kernel |
|
| CPEs | cpe:2.3:a:imaginationtech:ddk:*:*:*:*:*:*:*:* cpe:2.3:a:imaginationtech:ddk:26.1:rtm1:*:*:*:*:*:* cpe:2.3:o:google:android:-:*:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
|
| Vendors & Products |
Google
Google android Imaginationtech ddk Linux Linux linux Kernel |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Imaginationtech
Imaginationtech graphics Ddk |
|
| Vendors & Products |
Imaginationtech
Imaginationtech graphics Ddk |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Software installed and run as a non-privileged user may conduct improper GPU system calls to cause an integer overflow and map two GPU virtual addresses to the same physical address. One of these virutal mappings can be freed along with the physical page, allowing for a read/write UAF via the second mapping The second virtual mapping references a physical address that has been freed after the first virtual mapping has been freed. This allows the physical memory to be allocated (for example) by another process and read/written to. | |
| Title | GPU DDK - UAF read and/or write of arbitrary physical memory due to integer truncation in PMRDevPhysAddrOSMem | |
| Weaknesses | CWE-416 | |
| References |
|