Valhall GPU Kernel Driver: Write-what-where Condition
CVE-2022-41757 is a high-severity write-what-where condition vulnerability in Valhall GPU Kernel Driver from Arm, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version r38p2 as the first without the flaw, so updating Valhall GPU Kernel Driver to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.91% chance of exploitation within 30 days, higher than 61% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Valhall GPU Kernel Driver to r38p2 or a later version.
- Read the advisory on developer.arm.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Arm | Valhall GPU Kernel Driver | r29p0 up to, but not including, r38p2; r39p0 | r38p2 |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | NVD |
| CVSS 3.1 | 8.8 | High | CISA (ADP) |
Official description
An issue was discovered in the Arm Mali GPU Kernel Driver. A non-privileged user can make improper GPU processing operations to obtain write access to read-only memory, or obtain access to already freed memory. This affects Valhall r29p0 through r38p1 before r38p2, and r39p0 before r40p0.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Write-what-where Condition
Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
- Use OS-level preventative functionality integrated after the fact. Not a complete solution.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Valhall GPU Kernel Driver
- 7.7 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.5 High severity
- 7.8 High severity
Recent Write-what-where Condition vulnerabilities
- 8.2 High severity
Spotted an error? Tell us.