CVE-2026-80845 json
xfrm: avoid lock inversion in nat keepalive work
published 2026-09-04 2 mo ago modified 2026-10-19 20 d ago also EUVD-2026-71295
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
xfrm: avoid lock inversion in nat keepalive work
nat_keepalive_work() walks the state table while xfrm_state_walk() holds net->xfrm.xfrm_state_lock. Its callback then acquires x->lock, which conflicts with the delete path taking the same locks in reverse order via xfrm_state_delete() and __xfrm_state_delete(). This creates an AB-BA deadlock that is reported by lockdep when a NAT keepalive worker races with SA deletion.
Fix this by splitting the keepalive walk into two phases. First, collect the candidate states while the walk holds xfrm_state_lock and take a reference on each state. Then, after the walk completes, process each collected state and acquire x->lock without nesting it under xfrm_state_lock.
Patch / fix
- Linux Linux 6.12.108, 6.18.49, 7.1.13, 7.2.3, 7.3
- linux Debian 13 6.12.111-1
- linux Debian 14 7.1.13-1
- linux-6.12 Debian 12 6.12.111-1~deb12u1
debian advisories DEBIAN-CVE-2026-80845
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1017.17
- linux-riscv Ubuntu 26.04 LTS 7.0.0-42.42.1
- linux-oracle Ubuntu 26.04 LTS 7.0.0-1015.16
- linux-hwe-7.0 Ubuntu 24.04 LTS 7.0.0-42.42~24.04.1
- linux-oem-7.0 Ubuntu 26.04 LTS 7.0.0-1017.17
ubuntu advisories UBUNTU-CVE-2026-80845
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.2.5-1.1
opensuse advisories openSUSE-SU-2026:11773-1
- git.kernel.org/stable/c/ea09210462316e5235a25eccb11ad0708d86615e commit
- git.kernel.org/stable/c/5c86c895d1cac81a71ead3005084c6265cf6a7a5 commit
- git.kernel.org/stable/c/89ef3a2e1e4682ab82b0455ce113f8c39fb9e50d commit
- git.kernel.org/stable/c/a9fa05b7a1246797748d15771052639e0d3cabf1 commit
- git.kernel.org/stable/c/763fe700b7c58ad64fe5202c5638848244dd4127 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-80845 updated cvss 5.5
kernel: xfrm: avoid lock inversion in nat keepalive work
-
Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/ea09210462316e5235a25eccb11ad0708d86615e
- git.kernel.org /stable/c/5c86c895d1cac81a71ead3005084c6265cf6a7a5
- git.kernel.org /stable/c/89ef3a2e1e4682ab82b0455ce113f8c39fb9e50d
- git.kernel.org /stable/c/a9fa05b7a1246797748d15771052639e0d3cabf1
- git.kernel.org /stable/c/763fe700b7c58ad64fe5202c5638848244dd4127
Sources
- CVE List CVE-2026-80845
- NVD CVE-2026-80845
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.