CVE-2024-46725
Description
A flaw was found in the drm/amdgpu component of the Linux kernel. This out-of-bounds write vulnerability occurs due to an improper check of the ring type value. A local attacker with high privileges could exploit this flaw to cause data corruption, system instability, or potentially achieve privilege escalation.
Statement
This flaw will need a root/admin (PR:H) to exploit the OOB write.
Mitigation
To mitigate this issue, prevent the `amdgpu` kernel module from loading. This can be achieved by creating a blacklist entry. Note that this may impact functionality if an AMD GPU is in use. A system reboot is required for the changes to take effect.
Create a file `/etc/modprobe.d/blacklist-amdgpu.conf` with the following content:
blacklist amdgpuThen, regenerate the initramfs and reboot the system:
bashIf the system uses an AMD GPU for display or other critical functions, blacklisting this module may lead to loss of graphics or other hardware-related functionality.
dracut -f -v
reboot
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 | 6.7 | 7.8 | 7.8 |
| Attack Vector | Local | Local | Local |
| Attack Complexity | Low | Low | Low |
| Privileges Required | High | 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:L/PR:H/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)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
