CVE-2024-46801
Description
From CVE.org
In the Linux kernel, the following vulnerability has been resolved: libfs: fix get_stashed_dentry() get_stashed_dentry() tries to optimistically retrieve a stashed dentry from a provided location. It needs to ensure to hold rcu lock before it dereference the stashed location to prevent UAF issues. Use rcu_dereference() instead of READ_ONCE() it's effectively equivalent with some lockdep bells and whistles and it communicates clearly that this expects rcu protection.
Statement
A low impact use-after-free vulnerability was found in the Linux kernel's libfs subsystem. The get_stashed_dentry() helper in fs/libfs.c optimistically retrieves a stashed dentry but did not hold the RCU read lock while dereferencing the stashed location, so a concurrent dentry update could free the referenced memory, resulting in a use-after-free. A local attacker with the privileges needed to reach the affected path-lookup code could exploit this race to cause a kernel crash, that is, a denial of service. Red Hat assessed this flaw as Low impact with a CVSS 3.1 score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), lower than the CVE.org score of 7.8, because exploitation requires local access and privileges and Red Hat's assessment limits the practical impact to availability.
The affected code was introduced upstream in Linux kernel version 6.9 and is not present in the Red Hat Enterprise Linux 8 and 9 kernel bases; accordingly, Red Hat Enterprise Linux 8 and 9 kernel and kernel-rt streams and Red Hat's managed Hosted OpenShift (ARO and OSD) offerings are recorded as not affected. Red Hat Enterprise Linux 6 and 7 Extended Lifecycle Support streams are out of support scope for this flaw. The Fedora community kernel is affected and is tracked as delegated, with a fix pursued through the Fedora community kernel updates.
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).
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
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
