- Vulnerability/
- CVE-2025-21990
CVE-2025-21990: drm/amdgpu: NULL-check BO's backing store when determining GFX12 PTE flags
First published: Wed Apr 02 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: NULL-check BO's backing store when determining GFX12 PTE flags PRT BOs may not have any backing store, so bo->tbo.resource will be NULL. Check for that before dereferencing. (cherry picked from commit 3e3fcd29b505cebed659311337ea03b7698767fc)
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-21990?
CVE-2025-21990 is classified as a high-severity vulnerability due to its potential impact on system stability and security.
How do I fix CVE-2025-21990?
To fix CVE-2025-21990, update your Linux kernel to the latest version where the vulnerability is patched.
What systems are affected by CVE-2025-21990?
CVE-2025-21990 affects specific versions of the Linux kernel that handle DRM and AMD GPU functionalities.
What are the potential impacts of CVE-2025-21990?
Exploitation of CVE-2025-21990 can lead to system crashes or instability when handling graphics resources.
Who is responsible for addressing vulnerabilities like CVE-2025-21990?
Maintainers of the Linux kernel and system administrators are responsible for addressing vulnerabilities like CVE-2025-21990 by applying updates.
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/title
- agent/type
- agent/description
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/source
- agent/last-modified-date
- agent/author
- agent/tags
- agent/event
- vendor/linux
- canonical/linux kernel