Answer in brief
CVE-2026-31579 records a Unknown severity vulnerability in wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=900575aa33a3eaaef802b31de187a85c4a4b4bd0 <707607db2193591b68c0e70f814133472c185b1e || >=900575aa33a3eaaef802b31de187a85c4a4b4bd0 <9a9e69155b2091b8297afaf1533b8d68a3096841 || >=900575aa33a3eaaef802b31de187a85c4a4b4bd0 <1c52ef00e391144334f10995985c2f256d4be982 || >=900575aa33a3eaaef802b31de187a85c4a4b4bd0 <a1d0f6cbb962af29586e3e65a4bced1a5e39221f || >=900575aa33a3eaaef802b31de187a85c4a4b4bd0 <60a25ef8dacb3566b1a8c4de00572a498e2a3bf9 || 363cc6efdbb54bb06cd5034a69b41aae974a736f || >=5.7.7 <5.8 | 707607db2193591b68c0e70f814133472c185b1e, 9a9e69155b2091b8297afaf1533b8d68a3096841, 1c52ef00e391144334f10995985c2f256d4be982, a1d0f6cbb962af29586e3e65a4bced1a5e39221f, 60a25ef8dacb3566b1a8c4de00572a498e2a3bf9, 5.8 |
| Linux/Linuxgeneric | 5.8 | Not reported |
Published upstream
Apr 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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. ]
Quoted source text, attributed separately from HOL analysis.