CVE-2026-97487
Description
A flaw was found in the Linux kernel's Journaled File System (JFS). An unhandled error when initializing the file system block size during mount operations allows a local user with mount privileges to cause a Denial of Service (DoS). By attempting to mount an incompatible or crafted storage volume, an attacker can trigger a kernel assertion failure, resulting in an immediate system crash.
Statement
A low impact denial of service flaw was found in the Linux kernel's Journaled File System (JFS) implementation. During a JFS mount, the return value of sb_set_blocksize() is not handled; when setting the superblock block size fails, for example when the underlying device presents a block size larger than PAGE_SIZE, the mount continues and the first buffer head access reaches a BUG_ON assertion in folio_set_bh(), producing a kernel Oops or panic that crashes the system. A local user with privileges to mount filesystems (typically CAP_SYS_ADMIN) can trigger this by attempting to mount a crafted or incompatible JFS volume. Only system availability is affected; there is no impact on confidentiality or integrity.
Red Hat Product Security assessed this flaw as Low impact. Although the Red Hat CVSS:3.1 score of 5.5 (Moderate) reflects the availability impact of a kernel crash, realistic exploitation requires high local privileges and control over the block device being mounted, which limits practical risk and supports the lower severity rating. No Red Hat products are currently listed as affected: the kernel packages shipped in supported Red Hat Enterprise Linux, Red Hat In-Vehicle OS, and OpenShift Container Platform releases do not contain the vulnerable code, and the Red Hat Enterprise Linux 6 Extended Life-cycle Support kernel 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 | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart
While assertion is good for catching logic errors and reducing the chances of reaching more serious vulnerability conditions, an attacker can still cause a denial of service if they can trigger an assert statement, and if the scope of the assert() extends beyond the attacker's own session. For example, if a server handles multiple simultaneous connections, if an assert() occurs in one single connection that causes all other connections to be dropped, this could be a significant denial of service.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.