Vulnerability · Published Jul 25, 2026 · Assigned by Linux

CVE-2026-64525xfrm: move policy_bydst RCU sync from per-netns .exit to .pre_exit

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 5% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 95.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: xfrm: move policy_bydst RCU sync from per-netns .exit to .pre_exit The struct pernet_operations docstring in include/net/net_namespace.h explicitly warns against blocking RCU primitives in .exit handlers: Exit methods using blocking RCU primitives, such as synchronize_rcu(), should be implemented via exit_batch. [...] Please, avoid synchronize_rcu() at all, where it's possible. Note that a combination of pre_exit() and exit() can be used, since a synchronize_rcu() is guaranteed between the calls. xfrm_policy_fini() violates this: it calls synchronize_rcu() before freeing the policy_bydst hash tables (so no RCU reader is mid- traversal at free time), but runs from xfrm_net_ops.exit -- once per namespace -- so a cleanup_net() of N namespaces pays N full RCU grace periods serially. Use the documented pre_exit/exit split. Move the policy flush (and the workqueue drains it depends on) into a new .pre_exit handler; xfrm_policy_fini() then runs in .exit and frees the hash tables after the synchronize_rcu_expedited() that cleanup_net() guarantees between the two phases. Providing O(1) RCU grace periods per batch instead of O(N). Observed on Linux 6.18 with a workload doing unshare(CLONE_NEWNET) at ~13/sec sustained: cleanup_net() and the netns_wq rescuer kthread both stuck in xfrm_policy_fini()'s synchronize_rcu(), >300k struct net accumulated in the cleanup queue, Percpu in /proc/meminfo climbed to 130+ GB on 256-CPU hosts, and memcg OOMs followed. setup_net and __put_net counts were balanced, ruling out a refcount leak.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.94-1DEBIAN-CVE-2026-64525
Debian:14linux7.0.12-1DEBIAN-CVE-2026-64525
Ubuntu:24.04:LTSlinux6.8.0-146.146UBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux7.0.0-28.28UBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-aws6.8.0-1066.69UBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux-aws7.0.0-1009.9UBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1066.69~22.04.1UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-azure6.8.0-1070.78UBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux-azure7.0.0-1010.10UBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1070.78~22.04.1UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1068.75UBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1009.9UBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1068.75~22.04.1UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-gcp6.8.0-1070.78UBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux-gcp7.0.0-1008.8UBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1070.78~22.04.1UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-gke6.8.0-1065.73UBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux-gke7.0.0-1003.4UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1051.55UBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-28.28~24.04.1UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-ibm6.8.0-1066.67UBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux-ibm7.0.0-1010.10UBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1066.67~22.04.1UBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-146.146.1UBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-146.146.1~22.04.1UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1064.67UBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1016.16UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1064.67~22.04.1UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2016.16UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1064.67.1UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1038.42UBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1009.9UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-oracle6.8.0-1063.66UBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux-oracle7.0.0-1008.8UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux-raspi7.0.0-1015.15UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux-realtime7.0.0-28.28.1UBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-64525
Ubuntu:26.04:LTSlinux-riscv7.0.0-28.28.1UBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-146.146~22.04.1UBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-28.28.1~24.04.3UBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-64525
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-64525
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-64525

Affected products (as reported)

VendorProductVersions
Linux Linux 438b1f668ad58f46ce699bb48e4698a7839e3f9e – before bca6386dc08750fc7cdcbc7683473748ba3114b93733fce2871c9bca9dd18a1a23b1432ea215a094 – before 91cc13978ab0bc6f669139f53e7e613a860d10e0069daad4f2ae9c5c108131995529d5f02392c446 – before d14ae8ef88c2c6590e107db61b6adce148cec7b3069daad4f2ae9c5c108131995529d5f02392c446 – before 3e52417318473782012b236d0325bf7d2266a597b2faee12538b5b008eaef65a4201eb29cb5cefb3b66920a3348c0f63ba18365248fa21fbf0b3a93733a3149dd81a1e2f52b80ee1e0fc380b39f3d0286.12.83 – before 6.12.93
Linux Linux 7.0

References