CVE-2026-43091

xfrm: Wait for RCU readers during policy netns exit

Published May 6, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

xfrm: Wait for RCU readers during policy netns exit

xfrm_policy_fini() frees the policy_bydst hash tables after flushing the
policy work items and deleting all policies, but it does not wait for
concurrent RCU readers to leave their read-side critical sections first.

The policy_bydst tables are published via rcu_assign_pointer() and are
looked up through rcu_dereference_check(), so netns teardown must also
wait for an RCU grace period before freeing the table memory.

Fix this by adding synchronize_rcu() before freeing the policy hash tables.

Analysis

AI-generated

Technical impact

The vulnerability arises when the Linux kernel finalizes an XFRM network namespace by freeing the policy_bydst hash tables immediately after flushing policy work items, without waiting for concurrent RCU readers to exit their read‑side critical sections. Because these tables are published via rcu_assign_pointer and accessed through rcu_dereference_check, the premature release can trigger a use‑after‑free scenario. An attacker could potentially exploit this race to crash the kernel or manipulate privileged data, leading to denial of service or escalation of privileges within the affected system.

Affected Systems

The flaw is present in all versions of the Linux kernel that have not applied the patch that adds a synchronize_rcu() call before freeing the policy hash tables. No specific version range is listed; affected releases include any kernel built before the commit referenced in the advisory (e.g., 069daad4f2ae9c5c108131995529d5f02392c446).

Risk and Exploitability

The CVSS score is 7.8, indicating a high severity. The EPSS score is less than 1%, reflecting a very low likelihood of exploitation. The issue is not currently listed in CISA KEV, so no widespread exploitation is known. The exploit requires the ability to trigger a network‑namespace teardown while other contexts retain RCU references to the policy tables, which may limit the attack surface. Nevertheless, the potential for a kernel crash or privilege elevation warrants prompt action if the affected kernel version is in use.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the kernel patch that inserts synchronize_rcu() before freeing the policy_bydst tables, as referenced in the advisory commits.
  • Rebuild and install the updated kernel, then reboot into the new kernel image.
  • Verify that any network namespaces are cleanly removed before shutdown or system reconfiguration to avoid triggering the bug during normal operation.

Generated by OpenCVE AI on May 19, 2026 at 23:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8567-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8574-1 Linux kernel (GCP FIPS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8574-2 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8595-1 Linux kernel (Oracle) vulnerabilities
Ubuntu USN Ubuntu USN USN-8596-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8595-2 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8606-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8607-1 Linux kernel (Azure CVM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8608-1 Linux kernel (Azure FIPS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8609-1 Linux kernel (Azure CVM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8574-3 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8595-3 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8619-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-8665-1 Linux kernel (Raspberry Pi) vulnerabilities
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-368
CWE-416
CWE-788
Type Values Removed Values Added
Weaknesses CWE-368
CWE-416
Type Values Removed Values Added
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:*
Type Values Removed Values Added
Weaknesses CWE-368
CWE-416
Type Values Removed Values Added
Weaknesses CWE-368
CWE-416
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-368
CWE-416
Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: xfrm: Wait for RCU readers during policy netns exit xfrm_policy_fini() frees the policy_bydst hash tables after flushing the policy work items and deleting all policies, but it does not wait for concurrent RCU readers to leave their read-side critical sections first. The policy_bydst tables are published via rcu_assign_pointer() and are looked up through rcu_dereference_check(), so netns teardown must also wait for an RCU grace period before freeing the table memory. Fix this by adding synchronize_rcu() before freeing the policy hash tables.
Title xfrm: Wait for RCU readers during policy netns exit
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:24 PM
Reserved
May 1, 2026, 2:12 PM
Status
Modified
Published
May 6, 2026, 10:16 AM
Modified
Nov 11, 2026, 9:10 PM
Severity
Moderate
Public date
May 6, 2026, 12:00 AM