wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit
- 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 5.8, 6.12.114, 6.18.24, 6.19.14, 7.0.1
- 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: wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit wg_netns_pre_exit() manually acquires rtnl_lock() inside the pernet .pre_exit callback. This causes a hung task when another thread holds rtnl_mutex - the cleanup_net workqueue (or the setup_net failure rollback path) blocks indefinitely in wg_netns_pre_exit() waiting to acquire the lock. Convert to .exit_rtnl, introduced in commit 7a60d91c690b ("net: Add ->exit_rtnl() hook to struct pernet_operations."), where the framework already holds RTNL and batches all callbacks under a single rtnl_lock()/rtnl_unlock() pair, eliminating the contention window. The rcu_assign_pointer(wg->creating_net, NULL) is safe to move from .pre_exit to .exit_rtnl (which runs after synchronize_rcu()) because all RCU readers of creating_net either use maybe_get_net() • which returns NULL for a dying namespace with zero refcount - or access net->user_ns which remains valid throughout the entire ops_undo_list sequence. [ Jason: added __net_exit and __read_mostly annotations that were missing. ]
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 900575aa33a3eaaef802b31de187a85c4a4b4bd0 · fixed in 707607db2193591b68c0e70f814133472c185b1e; From 900575aa33a3eaaef802b31de187a85c4a4b4bd0 · fixed in 9a9e69155b2091b8297afaf1533b8d68a3096841; From 900575aa33a3eaaef802b31de187a85c4a4b4bd0 · fixed in 1c52ef00e391144334f10995985c2f256d4be982; From 900575aa33a3eaaef802b31de187a85c4a4b4bd0 · fixed in a1d0f6cbb962af29586e3e65a4bced1a5e39221f; From 900575aa33a3eaaef802b31de187a85c4a4b4bd0 · fixed in 60a25ef8dacb3566b1a8c4de00572a498e2a3bf9; From 5.7.7 · fixed in 5.8
- Linux Linux
5.8
- KernelLinux
From 5.8.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.24; From 6.19.0 · fixed in 6.19.14; From 6.20.0 · fixed in 7.0.1