CVE-2026-53239

Description

A flaw was found in the Linux kernel. A race condition exists in the xfrm policy handling, specifically within the xfrm_policy_bysel_ctx() function. This flaw allows for a use-after-free vulnerability, where memory is accessed after it has been released. This can lead to system instability or a denial of service (DoS), making the system unresponsive or causing it to crash.

Statement

A race in xfrm_policy_bysel_ctx() can leave an inexact policy bin pointer usable after xfrm_hash_rebuild() has flushed and freed the same bin through kfree_rcu(). A local attacker who can issue the relevant XFRM netlink policy operations may race XFRM_MSG_DELPOLICY against XFRM_MSG_NEWSPDINFO and trigger a use-after-free in the policy pruning path. For the CVSS the PR:L is used because CAP_NET_ADMIN may be available to a container root, netns root, or delegated network administration service account, which is weaker than full host administrator control in practical risk terms. The issue is not directly network reachable because the trigger is local XFRM control plane activity rather than inbound IPsec packet traffic. Impact is at least local denial of service via kernel crash. In the paranoid interpretation, the UAF may allow confidentiality and integrity impact or privilege escalation and 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).

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.