CVE-2026-23158

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-02-14. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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:

gpio: virtuser: fix UAF in configfs release path

The gpio-virtuser configfs release path uses guard(mutex) to protect the device structure. However, the device is freed before the guard cleanup runs, causing mutex_unlock() to operate on freed memory.

Specifically, gpio_virtuser_device_config_group_release() destroys the mutex and frees the device while still inside the guard(mutex) scope. When the function returns, the guard cleanup invokes mutex_unlock(&dev->lock), resulting in a slab use-after-free.

Limit the mutex lifetime by using a scoped_guard() only around the activation check, so that the lock is released before mutex_destroy() and kfree() are called.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

February 14, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

gpio: virtuser: fix UAF in configfs release path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/815a8e3bf72811d402b30bd4a53cde5e9df7a563
generic

gpio: virtuser: fix UAF in configfs release path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7bec90f605cfb138006f5ba575f2310593347110
generic

gpio: virtuser: fix UAF in configfs release path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/53ad4a948a4586359b841d607c08fb16c5503230

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.69osv

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)6.12.69-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (98 versions)6.18.9-1

Weakness Classification(1)

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

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 5× in last 7d / 24× 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 175 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23158?
CVE-2026-23158 is a high vulnerability published on February 14, 2026. In the Linux kernel, the following vulnerability has been resolved: gpio: virtuser: fix UAF in configfs release path The gpio-virtuser configfs release path uses guard(mutex) to protect the device structure. However, the device is freed before the guard cleanup runs, causing mutex_unlock() to…
When was CVE-2026-23158 disclosed?
CVE-2026-23158 was first published in the National Vulnerability Database on February 14, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23158 actively exploited?
CVE-2026-23158 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-23158?
CVE-2026-23158 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23158?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23158, 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-23158

Explore →

Is Your Infrastructure Affected by CVE-2026-23158?

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