CVE-2026-31579wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit
- 5.5MediumCVSS base score
- 0.15%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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
ID reserved
By Linux
- 46 days later
· 46 days later
Published
- 7 months later
· 7 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.15% · top 95% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 900575aa33a3eaaef802b31de187a85c4a4b4bd0 – < 707607db2193591b68c0e70f814133472c185b1e
- affected 900575aa33a3eaaef802b31de187a85c4a4b4bd0 – < 9a9e69155b2091b8297afaf1533b8d68a3096841
- affected 900575aa33a3eaaef802b31de187a85c4a4b4bd0 – < 1c52ef00e391144334f10995985c2f256d4be982
- affected 900575aa33a3eaaef802b31de187a85c4a4b4bd0 – < a1d0f6cbb962af29586e3e65a4bced1a5e39221f
- affected 900575aa33a3eaaef802b31de187a85c4a4b4bd0 – < 60a25ef8dacb3566b1a8c4de00572a498e2a3bf9
- affected 363cc6efdbb54bb06cd5034a69b41aae974a736f
- affected 5.7.7 – < 5.8
- affected 5.8
- unaffected < 5.8
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.24 – ≤ 6.18.*
- unaffected 6.19.14 – ≤ 6.19.*
- unaffected 7.0.1 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References5
- https://git.kernel.org/stable/c/707607db2193591b68c0e70f814133472c185b1e (opens in a new tab)
- https://git.kernel.org/stable/c/9a9e69155b2091b8297afaf1533b8d68a3096841 (opens in a new tab)
- https://git.kernel.org/stable/c/1c52ef00e391144334f10995985c2f256d4be982 (opens in a new tab)
- https://git.kernel.org/stable/c/a1d0f6cbb962af29586e3e65a4bced1a5e39221f (opens in a new tab)
- https://git.kernel.org/stable/c/60a25ef8dacb3566b1a8c4de00572a498e2a3bf9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-25472 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-31579)Record last updated .