CVE-2026-80985
Description
A flaw was found in the Linux kernel's Server Message Block over Remote Direct Memory Access (SMC-Rv2) protocol implementation. The smc_llc_rmt_delete_rkey() and smc_llc_save_add_link_rkeys() functions incorrectly handle oversized LLC messages, reading beyond the intended message boundaries. This can lead to the processing of stale or unintended data from previous messages, potentially resulting in information disclosure or data corruption. A remote attacker could exploit this vulnerability to gain access to sensitive information or cause system instability.
Statement
This flaw is rated as having Important impact because a network peer capable of exchanging SMC-R traffic can trigger out-of-bounds reads in the kernel, leading to potential denial of service or unexpected memory access. In standard Red Hat Enterprise Linux deployments, overall exposure is limited because Shared Memory Communications over RDMA requires specialized hardware interfaces and explicit protocol configuration rather than default TCP/IP operations.
Mitigation
To mitigate this vulnerability, prevent the Shared Memory Communications (`smc`) kernel module from loading on the system:
1. Add a configuration rule in `/etc/modprobe.d/` to disable autoloading:
echo "install smc /bin/true" >> /etc/modprobe.d/disable-smc.conf
2. If the module is already loaded, attempt to unload it:
modprobe -r smc
Warning: Disabling this module prevents applications from establishing SMC (SMC-R/SMC-D) connections, which may cause them to fall back to standard TCP or fail if SMC is strictly required. If the module cannot be unloaded because it is currently in use, a full system reboot is necessary to enforce the mitigation.
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.1 | N/A | 8.2 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | None |
| Integrity Impact | None | N/A | Low |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.