CVE-2026-89595
Description
A flaw was found in the Linux kernel's fsnotify subsystem, affecting fanotify and inotify. A race condition can occur during concurrent updates to event marks, where the object mask becomes stale. This can lead to a denial of service or information disclosure, as events such as file modifications (e.g., FAN_MODIFY, IN_MODIFY) may not be properly reported to applications monitoring file system activity.
Statement
A moderate vulnerability was found in the Linux kernel's fsnotify subsystem, which backs the fanotify and inotify file-monitoring interfaces. When multiple marks attached to the same object are updated concurrently, a race condition between the recalculation of the aggregate object mask and a concurrent update to another mark can leave the object mask stale. As a result, filesystem events such as file modifications (FAN_MODIFY / IN_MODIFY) may not be reported to applications that monitor filesystem activity even though the corresponding watch is in place, which can degrade security, auditing, and monitoring tools that rely on reliable event notification and lead to a denial of service or information disclosure through missed file modification events. Red Hat Product Security rates this flaw Moderate (CVSS 3.1 score 5.5, vector AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H): exploitation requires local access, the ability to create fanotify or inotify watches, and a carefully timed race between concurrent mark updates on the same object. The kernel and kernel-rt packages in Red Hat Enterprise Linux 7, 8, and 9 and the RHCOS kernels shipped in OpenShift Container Platform 4 are affected. For these affected Red Hat streams the fix is currently deferred and no update is planned at this time, reflecting the limited practical exploitability of the issue (local access and precise concurrent-update timing are required, and the kernel team assessed the risk as low); the residual risk is that applications relying on fanotify or inotify event notification may miss file modification events when concurrent watch updates race, with no direct impact on kernel memory integrity.
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)
Integrity,Other
Technical Impact: Alter Execution Logic; Unexpected State
The attacker can gain access to otherwise unauthorized resources.
Integrity,Other
Technical Impact: Modify Application Data; Modify Files or Directories; Modify Memory; Other
Race conditions such as this kind may be employed to gain read or write access to resources which are not normally readable or writable by the user in question.
Integrity,Other
Technical Impact: Other
The resource in question, or other resources (through the corrupted one), may be changed in undesirable ways by a malicious user.
Non-Repudiation
Technical Impact: Hide Activities
If a file or other resource is written in this method, as opposed to in a valid way, logging of the activity may not occur.
Non-Repudiation,Other
Technical Impact: Other
In some cases it may be possible to delete files a malicious user might not otherwise have access to, such as log files.
Other
Technical Impact: Unexpected State
The product may perform invalid actions when the resource is in an unexpected state.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.