CVE-2026-68415

Description

A flaw was found in the Linux kernel's xfrm (IPSec framework) component. A vulnerability exists where the xfrm_state_gc_task can attempt to dereference stale callback data after a failed Internet Protocol Traffic Flow Security (IPTFS) state setup and subsequent module unload. This can lead to a kernel panic and system crash, resulting in a Denial of Service (DoS) for the affected system.

Statement

A stale callback pointer can remain in an XFRM state when IPTFS mode initialization or clone fails before mode specific data is published. The temporary module reference is dropped, but the dead state can still carry the cached mode callback table until deferred xfrm_state_gc_task runs after xfrm_iptfs has been unloaded. This creates a use-after-free like condition where GC may dereference callbacks that belong to an unloaded module, leading at least to a kernel crash and denial of service. For the CVSS the PR:L is used in the paranoid score because XFRM control can be delegated to a reduced capability root, container root, or service account with CAP_NET_ADMIN in some deployments, even though typical module unload control is more privileged. The issue is local and not directly network reachable. Impact is at least local denial of service via kernel crash. In the worst still defensible interpretation, the stale callback table after module unload is a memory corruption candidate and may allow confidentiality or integrity impact, so this should be reviewed manually.

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 Score4.7N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityHighN/ALow
Privileges RequiredLowN/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:L/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.