CVE-2026-80979

Description

A flaw was found in the Linux kernel's Shared Memory Communications (SMC) component. During connection termination, the SMC component may fail to properly unregister a connection before draining its receive tasklet. This can lead to a use-after-free vulnerability, where a freed memory buffer is subsequently dereferenced. A local attacker could potentially exploit this to cause a system crash, resulting in a denial of service, or potentially achieve arbitrary code execution.

Statement

A race in the SMC-D teardown path can leave a freed connection registered in the smcd conn table while device IRQ handling can still re-arm the rx tasklet after tasklet_kill has returned. In the DMB nocopy path the send buffer can be freed after the drain, so the re-armed tasklet may later dereference freed memory and crash the kernel. For the CVSS the PR:N is used because an adjacent SMC-D peer may only need reachability to a service using SMC-D and not a local account on the victim. The attack is not expected to be directly Internet reachable and is mainly relevant to systems using SMC-D over ISM or similar adjacent fabric deployments. Impact is at least denial of service via kernel crash and in the paranoid interpretation may include confidentiality or integrity impact because the bug class is use-after-free in kernel memory.

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 HatNVDcve.org
Base Score5.1N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityHighN/ALow
Privileges RequiredNoneN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.