CVE-2026-89633
Description
A flaw was found in the Linux kernel's Server Message Block (SMB) client. The coalesce_t2() function processes server-supplied DataOffset fields without proper validation against buffer boundaries. A remote attacker could exploit this by crafting malicious SMB responses. This could lead to out-of-bounds read and write operations, potentially resulting in information disclosure or arbitrary code execution.
Statement
This vulnerability is rated as Important because an attacker controlling an SMB server can trigger kernel heap corruption on a client system, though exploitation requires an active connection to an untrusted or compromised file share. Under default configurations in Red Hat Enterprise Linux, the kernel CIFS client negotiates modern SMB dialects rather than the legacy SMBv1 protocol where this transaction reassembly logic resides. Consequently, systems are only exposed when administrators explicitly configure mounts using deprecated SMBv1 or establish connections to untrusted endpoints.
Mitigation
Prevent the `cifs` kernel module from loading if mounting SMB network file shares is not required.
1. Create a configuration file to blacklist the module:
text
echo "install cifs /bin/true" >> /etc/modprobe.d/disable-cifs.conf
echo "blacklist cifs" >> /etc/modprobe.d/disable-cifs.conf
2. If the module is currently loaded into memory, unload it:
text
modprobe -r cifs
Caveats:
Disabling this module prevents the system from mounting remote CIFS and SMB file systems. If active SMB shares are in use, all shares must be unmounted before unloading the module, or a system restart is required to apply the changes.
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).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 8 | N/A | 9.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | Required | 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:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
Confidentiality
Technical Impact: Bypass Protection Mechanism
Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.
Other
Technical Impact: Varies by Context
The read operation could produce other 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.