CVE-2022-50035
Description
A flaw was found in the Linux kernel's AMD GPU driver. Improper error handling during command submission causes an internal lock to be released twice, leading to a reference count underflow and a use-after-free condition where memory is accessed after being released. A local user with access to an AMD graphics device could exploit this vulnerability to cause a Denial of Service (DoS) through a system crash or potentially escalate privileges.
Statement
This vulnerability is evaluated as having Moderate impact because exploitation requires local access on a system with dedicated AMD GPU hardware and direct rendering capabilities, limiting the blast radius to a localized denial of service or potential privilege escalation. The issue occurs when error handling within the AMD display driver incorrectly handles mutex unlocking, triggering a reference count underflow. Supported Red Hat Enterprise Linux releases are not affected by this flaw because the vulnerable code sequence was never introduced into Red Hat kernel builds.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7 | 7.8 | 7.8 |
| Attack Vector | Local | Local | Local |
| Attack Complexity | High | Low | Low |
| Privileges Required | Low | Low | Low |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Unchanged |
| Confidentiality | High | High | High |
| Integrity Impact | High | High | High |
| Availability Impact | High | High | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Availability,Integrity
Technical Impact: DoS: Crash, Exit, or Restart; Modify Memory; Unexpected State
When the product is operating in a concurrent environment and repeatedly unlocks a critical resource, the consequences will vary based on the type of lock, the lock's implementation, and the resource being protected. In some situations such as with semaphores, the resources are pooled and extra calls to unlock will increase the count for the number of available resources, likely resulting in a crash or unpredictable behavior when the system nears capacity.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.