CVE-2024-42306
Description
A flaw was found in the Linux kernel's Universal Disk Format (UDF) filesystem. When a UDF filesystem's block bitmap, which manages disk space, becomes corrupted, the kernel attempts to use this invalid data. This can lead to subsequent disk space allocation failures, potentially causing system instability or a denial of service (DoS) for a local user.
Mitigation
If UDF filesystem support is not required on a system, the `udf` kernel module can be blacklisted to prevent it from being loaded.
To blacklist the `udf` module:
1. Create a file named `/etc/modprobe.d/blacklist-udf.conf` with the following content:
`blacklist udf`
2. Regenerate the initramfs to apply the change. For Red Hat Enterprise Linux 7, 8, and 9, use `dracut -f -v`. For Red Hat Enterprise Linux 6, use `mkinitrd -f -v`.
3. Reboot the system for the changes to take effect.
This action may impact functionality for systems that rely on UDF filesystem access.
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)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)
An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excessive consumption of resources such as memory and CPU.
Confidentiality
Technical Impact: Read Memory; Read Files or Directories
An attacker could read confidential data if they are able to control resource references.
Integrity,Confidentiality,Availability
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
