Software installed and run as a non-privileged user may conduct improper GPU system calls to gain write permissions to memory buffers exported as read-only.
This is caused by improper handling of the memory protections for the buffer resource.
Weakness
The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Ddk | Imaginationtech | 23.3-rtm (including) | 23.3-rtm (including) |
| Ddk | Imaginationtech | 24.1 (including) | 24.1 (including) |
| Ddk | Imaginationtech | 24.2 (including) | 24.2 (including) |
| Ddk | Imaginationtech | 24.2-rtm1 (including) | 24.2-rtm1 (including) |
| Ddk | Imaginationtech | 24.2-rtm2 (including) | 24.2-rtm2 (including) |
| Ddk | Imaginationtech | 24.3 (including) | 24.3 (including) |
| Ddk | Imaginationtech | 25.1 (including) | 25.1 (including) |
| Ddk | Imaginationtech | 25.2 (including) | 25.2 (including) |
| Ddk | Imaginationtech | 25.2-rtm (including) | 25.2-rtm (including) |
Potential Mitigations
- Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.