CVE-2026-80985

8.2

Linux · Kernel

A buffer handling flaw in the Linux kernel SMC-Rv2 implementation allows oversized messages to cause memory corruption, potentially leading to unauthorized rtoken deletion or installation.

Executive summary

A memory handling vulnerability in the Linux kernel SMC-Rv2 subsystem could allow remote attackers to perform unauthorized operations, resulting in service disruption or integrity compromise.

Vulnerability

The vulnerability exists in the smc_llc_rmt_delete_rkey and smc_llc_save_add_link_rkeys functions, which fail to properly validate the size of incoming SMC-Rv2 messages. An unauthenticated remote attacker can supply oversized messages, causing the kernel to process stale data from the receive buffer and leading to improper rtoken manipulation.

Business impact

The flaw carries a CVSS score of 8.2, reflecting a high risk due to the potential for service disruption (Denial of Service) and unauthorized integrity changes. Successful exploitation could lead to system instability or the corruption of critical network session tokens, potentially allowing for unauthorized access to data streams or denial of service for legitimate users.

Remediation

Immediate Action: Update the Linux kernel to version 6.18.50, 7.2.4, or later versions where the fix has been backported.

Proactive Monitoring: Monitor system logs for kernel panics or unexpected network stack errors, particularly those related to the SMC-Rv2 subsystem.

Compensating Controls: If patching is not immediately feasible, consider disabling the SMC (Shared Memory Communications) protocol via kernel module configuration if it is not required for production workloads.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the high CVSS severity and the critical nature of the Linux kernel, organizations should prioritize testing and deploying the identified security patches. Administrators must verify their kernel versions and apply the upstream fixes or distribution-specific updates as soon as they become available to mitigate the risk of remote memory corruption and service instability.

More Linux CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief No CVSS score yet; tracked as early warning
  3. Analyst report written
  4. Published in the daily brief high section

Sources