CVE-2026-98682
Description
A flaw was found in the Linux kernel's Server Message Block (SMB) client subsystem. Due to improper synchronization during server-side file copy and clone operations, pending write operations are not drained before copying begins. A local user could exploit this timing issue during copy operations to overwrite newly copied data with stale data, resulting in file corruption.
Statement
The SMB client does not fully serialize server-side copy or clone operations against asynchronous writeback and cached pages for the destination file. An in-flight destination write can complete after the server has copied or cloned the requested range and can restore stale cached data over the new server-side contents. This produces persistent destination file corruption and was observed during generic/363 testing against Windows Server. For the CVSS the PR:L because a local user or process with access to the SMB mount and permission to copy or clone into the destination can reach the affected paths without administrative capabilities. AC:H applies because successful triggering depends on a timing window between asynchronous destination I/O and the server-side operation. The issue is not directly reachable through unsolicited network traffic because the vulnerable operation is initiated on the SMB client, although the affected file and copy operation involve a remote SMB server. The confirmed impact is integrity loss through file corruption. There is no supported kernel memory corruption or information disclosure primitive. The worst still defensible availability impact is loss of access to corrupted application data rather than a kernel crash or privilege escalation.
Mitigation
Mitigation for this issue is either not available or the currently available options don't 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 | 2.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | High | 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 | Low | N/A | N/A |
| Availability Impact | None | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Understanding the Weakness (CWE)
Other
Technical Impact: Varies by Context
When code does not follow the instructions for resource management, it can lead to unexpected behaviors and potentially exploitable states.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.