CVE-2023-53804
Description
A flaw was found in the Linux kernel's NILFS2 file system. A local user can trigger a use-after-free flaw during file system unmount operations when releasing cached file structures. This issue can lead to kernel memory corruption, resulting in a Denial of Service (DoS) or potential privilege escalation.
Statement
This vulnerability presents no operational impact for Red Hat Enterprise Linux environments because the NILFS2 file system module is neither built nor shipped with Red Hat enterprise kernels. In upstream kernels where this filesystem is enabled, local users performing unmount operations could trigger memory corruption through a use-after-free condition during inode teardown. Because the underlying code is entirely absent from Red Hat enterprise products, no exposure exists for supported installations.
Mitigation
To mitigate this vulnerability, prevent the nilfs2 kernel module from loading:
1. Create a configuration file to disable the module:
# echo "install nilfs2 /bin/true" > /etc/modprobe.d/disable-nilfs2.conf
2. If the module is currently loaded, unload it:
# modprobe -r nilfs2
Caveat: Disabling the module prevents the system from mounting NILFS2 filesystems. If the module is currently in use, a system restart is required for the changes to take effect.
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 | 6.7 | N/A | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | High | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:H/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
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.