Protected-file overwrite via GPU memory wrapping
Published Dec 28, 2024 · Updated Dec 28, 2024
Improper permission handling in Imagination Technologies Graphics DDK 1.13 RTM through 24.2 RTM2 allows local users to overwrite read-only files. PVRSRVBridgePhysmemWrapExtMem lets the GPU kernel driver write into read-only system files, such as libc.so, when those files are mapped into application memory. A non-privileged application with access to the affected GPU driver can corrupt protected file-backed memory and the processes that use it.
Summary
What happened
Improper permission handling in Imagination Technologies Graphics DDK 1.13 RTM through 24.2 RTM2 allows local users to overwrite read-only files. PVRSRVBridgePhysmemWrapExtMem lets the GPU kernel driver write into read-only system files, such as libc.so, when those files are mapped into application memory. A non-privileged application with access to the affected GPU driver can corrupt protected file-backed memory and the processes that use it.
The record
- CVE
- CVE-2024-43705
- Published
- Dec 28, 2024
- Updated
- Dec 28, 2024
- Vendor
- Imagination Technologies
- Product
- Graphics DDK
- Classifications
- CWE-280, CAPEC-679, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 28, 2024CVE publishedPublication date reported by the CVE source.
- Dec 28, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.13 RTM <=24.2 RTM2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo