CVE-2026-31579

MEDIUMCVSS · not yet scored5.5
EchelonGraph scoreLOW confidence

Score 5.5 from GitHub Security Advisory published 2026-04-24.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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. ]

CVSS v3
—
EG Score
5.5(low)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

April 24, 2026

Last Modified

June 14, 2026

References (4)

Vendor Advisories for CVE-2026-31579(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.24—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (129 versions)6.19.14-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 212 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-11 14:52 UTCEPSS rescore
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-04 03:16 UTCOSV refresh
  10. 2026-09-02 14:11 UTCEPSS rescore
  11. 2026-09-01 13:53 UTCEPSS rescore
  12. 2026-09-01 04:39 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-24 14:17 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 14:52 UTCEG score recompute
  3. 2026-08-17 14:52 UTCVendor advisory
  4. 2026-08-17 14:52 UTCGHSA enrichment
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 05:48 UTCEG score recompute
  8. 2026-08-16 05:48 UTCVendor advisory
  9. 2026-08-16 05:48 UTCGHSA enrichment
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 04:08 UTCEG score recompute
  13. 2026-08-14 04:08 UTCVendor advisory
  14. 2026-08-14 04:08 UTCGHSA enrichment
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-12 23:44 UTCEG score recompute
  17. 2026-08-12 23:44 UTCVendor advisory
  18. 2026-08-12 23:44 UTCGHSA enrichment
  19. 2026-08-12 13:50 UTCEPSS rescore
  20. 2026-08-12 00:57 UTCEG score recompute
  21. 2026-08-12 00:57 UTCVendor advisory
  22. 2026-08-12 00:57 UTCGHSA enrichment
  23. 2026-08-11 02:10 UTCEG score recompute
  24. 2026-08-11 02:10 UTCVendor advisory
  25. 2026-08-11 02:10 UTCGHSA enrichment
  26. 2026-08-11 00:00 UTCEPSS rescore
  27. 2026-08-10 02:08 UTCVendor advisory
  28. 2026-08-10 02:08 UTCGHSA enrichment
  29. 2026-08-09 03:20 UTCEG score recompute
  30. 2026-08-09 03:20 UTCVendor advisory
  31. 2026-08-09 03:20 UTCGHSA enrichment
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-07 20:34 UTCEG score recompute
  34. 2026-08-07 20:34 UTCVendor advisory
  35. 2026-08-07 20:34 UTCGHSA enrichment
  36. 2026-08-06 21:47 UTCEG score recompute
  37. 2026-08-06 21:47 UTCVendor advisory
  38. 2026-08-06 21:47 UTCGHSA enrichment
  39. 2026-08-06 13:46 UTCEPSS rescore
  40. 2026-08-05 22:57 UTCEG score recompute
  41. 2026-08-05 22:57 UTCVendor advisory
  42. 2026-08-05 22:57 UTCGHSA enrichment
  43. 2026-08-05 19:17 UTCEPSS rescore
  44. 2026-08-04 15:10 UTCEPSS rescore
  45. 2026-08-04 10:38 UTCEPSS rescore
  46. 2026-08-03 21:04 UTCEG score recompute
  47. 2026-08-03 21:04 UTCVendor advisory
  48. 2026-08-03 21:04 UTCGHSA enrichment
  49. 2026-08-03 10:36 UTCEPSS rescore
  50. 2026-08-02 11:22 UTCEG score recompute
  51. 2026-08-02 11:22 UTCVendor advisory
  52. 2026-08-02 11:22 UTCGHSA enrichment
  53. 2026-08-02 02:27 UTCEPSS rescore
  54. 2026-08-01 04:16 UTCEPSS rescore
  55. 2026-07-30 16:27 UTCEPSS rescore
  56. 2026-07-30 01:30 UTCEPSS rescore
  57. 2026-07-28 15:36 UTCEPSS rescore
  58. 2026-07-26 14:54 UTCEPSS rescore
  59. 2026-07-26 14:54 UTCEPSS rescore
  60. 2026-07-25 14:18 UTCEPSS rescore
  61. 2026-07-25 14:17 UTCEPSS rescore
  62. 2026-07-24 14:17 UTCEPSS rescore
  63. 2026-07-23 14:18 UTCEPSS rescore
  64. 2026-07-23 14:18 UTCEPSS rescore
  65. 2026-07-23 03:08 UTCEG score recompute
  66. 2026-07-22 14:08 UTCEPSS rescore
  67. 2026-07-22 14:08 UTCEPSS rescore
  68. 2026-07-21 15:24 UTCEPSS rescore
  69. 2026-07-21 15:24 UTCEPSS rescore
  70. 2026-07-20 17:08 UTCEPSS rescore
  71. 2026-07-20 17:08 UTCEPSS rescore
  72. 2026-07-19 22:48 UTCOSV refresh
  73. 2026-07-19 14:31 UTCEPSS rescore
  74. 2026-07-19 14:31 UTCEPSS rescore
  75. 2026-07-19 02:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2026-31579?
CVE-2026-31579 is a medium vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: wireguard: device: use exitrtnl callback instead of manual rtnllock in pre_exit wgnetnspreexit() manually acquires rtnllock() inside the pernet .pre_exit callback. This causes a hung task when another thread holds rtnlmutex - the…
When was CVE-2026-31579 disclosed?
CVE-2026-31579 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31579 actively exploited?
CVE-2026-31579 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.8% of all scored CVEs.
How do I remediate CVE-2026-31579?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31579, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31579

Explore →

Is Your Infrastructure Affected by CVE-2026-31579?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs