xfrm: avoid lock inversion in nat keepalive work
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.108, 6.18.49, 7.1.13, 7.2.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux 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 Linux
6.11
- KernelLinux
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