CVE-2024-50288
Description
A flaw was found in the Linux kernel's Virtual Video (vivid) driver. A local user can exploit this vulnerability to trigger a Denial of Service (DoS) via a system crash. When a video capture queue requests more buffers than the driver's internal tracking array supports, an out-of-bounds write occurs, corrupting kernel memory.
Mitigation
To mitigate this vulnerability, prevent the vivid kernel module from being loaded:
1. Add configuration entries to blacklist and disable the module:
# echo "blacklist vivid" >> /etc/modprobe.d/blacklist-vivid.conf
# echo "install vivid /bin/true" >> /etc/modprobe.d/blacklist-vivid.conf
2. If the module is currently loaded into memory, unload it:
# modprobe -r vivid
Warning: Unloading the module or blacklisting it will disable virtual video capture test capabilities. If the driver is actively in use and cannot be removed dynamically, a system reboot will be required to ensure the module is not loaded.
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).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | 5.5 | 7.8 |
| Attack Vector | Local | Local | Local |
| Attack Complexity | Low | Low | Low |
| Privileges Required | Low | Low | Low |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Unchanged |
| Confidentiality | None | None | High |
| Integrity Impact | None | None | High |
| Availability Impact | High | High | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
