CVE-2026-97926
Description
A flaw was found in the Linux kernel's Unix File System (UFS) driver. When reading filesystem metadata from storage, the driver fails to validate cylinder group indices and rotor positions before caching them. A local attacker capable of mounting a specially crafted filesystem image could exploit this flaw to trigger out-of-bounds memory access, leading to a system crash and Denial of Service (DoS) or memory corruption.
Statement
A moderate impact out-of-bounds memory access flaw was found in the Linux kernel's Unix File System (UFS) driver. When reading a mounted UFS filesystem, ufs_read_cylinder() copies the cylinder group index (cg_cgx) and the rotor positions (cg_rotor, cg_frotor, cg_irotor) from the on-disk cylinder group metadata without validation and caches them. These cached values are later used as indices during block and inode allocation: an out-of-range cylinder group index causes a 32-bit write beyond the end of the s_csp cylinder summary allocation, and out-of-range rotor positions cause the unsigned bitmap scan length to wrap, driving ubh_scanc() far past the cylinder group buffers. A local attacker able to mount a specially crafted UFS filesystem image could exploit this flaw to trigger out-of-bounds kernel memory reads and writes, resulting in a system crash and denial of service or memory corruption. Exploitation requires local access and the ability to mount a filesystem image, which limits practical exposure and is reflected in the moderate impact rating despite the CVSS 3.1 base score of 7.0. The Red Hat Enterprise Linux 7, 8, 9, and 10, Red Hat In-Vehicle OS, and OpenShift 4 and 5 kernel builds recorded in this flaw are not affected because the vulnerable code is not present in those builds; the Red Hat Enterprise Linux 6 Extended Lifecycle Support stream is out of 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).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7 | N/A | 7 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | High | N/A | High |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | Required |
| 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:H/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/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.