CVE-2024-39486
Description
A race condition was found in the Linux kernel. The rm_file_update_pid() only increments the refcount of a struct pid after storing a pointer to it in filp->pid, dropping the dev->filelist_mutex, resulting in a use-after-free vulnerability.
Statement
A moderate-severity use-after-free vulnerability was found in the Linux kernel DRM subsystem. drm_file_update_pid() stored a pointer to a struct pid in filp->pid and dropped dev->filelist_mutex before incrementing that pid's refcount, so two processes racing through drm_file_update_pid() could cause a struct pid to reach refcount zero and be freed while another process still held a reference to it, resulting in a use-after-free. A local user with access to a DRM device could trigger this race to crash the system (denial of service); the race is considered difficult to hit and, per the upstream advisory, requires a kernel built with CONFIG_PREEMPT_RCU. Red Hat rates this flaw as Moderate impact because the race condition cannot result in loss of confidentiality or integrity (RH CVSS 5.5, availability-only impact), which is lower than the severity assigned by NIST (7.0) and the CVE.org record (7.8). Within Red Hat's product portfolio, the kernel and kernel-rt packages in Red Hat Enterprise Linux 9 are affected and fixes are being pursued through the Red Hat kernel team; Red Hat Enterprise Linux 8, Red Hat managed OpenShift (OSD and ARO) offerings, and Fedora are not affected, while the Red Hat Enterprise Linux 6 and 7 ELS streams are out of active support scope.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
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 | 5.5 | 7 | 7.8 |
| Attack Vector | Local | Local | Local |
| Attack Complexity | Low | High | Low |
| Privileges Required | Low | Low | Low |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Unchanged |
| Confidentiality | None | High | High |
| Integrity Impact | None | High | 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:H/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
Red Hat CVSS v3 Score Explanation
The exploitability of the race condition cannot result in loss of confidentiality or integrity,which is why CVSS has been marked as such
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
When a race condition makes it possible to bypass a resource cleanup routine or trigger multiple initialization routines, it may lead to resource exhaustion.
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability
When a race condition allows multiple control flows to access a resource simultaneously, it might lead the product(s) into unexpected states, possibly resulting in a crash.
Confidentiality,Integrity
Technical Impact: Read Files or Directories; Read Application Data
When a race condition is combined with predictable resource names and loose permissions, it may be possible for an attacker to overwrite or access confidential data (CWE-59).
Access Control
Technical Impact: Execute Unauthorized Code or Commands; Gain Privileges or Assume Identity; Bypass Protection Mechanism
This can have security implications when the expected synchronization is in security-critical code, such as recording whether a user is authenticated or modifying important state information that should not be influenced by an outsider.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.