CVE-2026-23158: gpio: virtuser: fix UAF in configfs release path

Published Feb 14, 2026
·
Updated

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 mutexunlock() to operate on freed memory.

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

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

Affected Software

10 affected components
linux/kernel
Linux Linux kernel>=6.11<6.12.69
Linux Linux kernel>=6.13<6.18.9
Linux Linux kernel=6.19-rc1
Linux Linux kernel=6.19-rc2
Linux Linux kernel=6.19-rc3
Linux Linux kernel=6.19-rc4
Linux Linux kernel=6.19-rc5
Linux Linux kernel=6.19-rc6
Linux Linux kernel=6.19-rc7

Event History

Feb 14, 2026
CVE Published
via MITRE·04:01 PM
Data Sourced
via MITRE·04:01 PM
Description
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-23158?

The severity of CVE-2026-23158 is considered moderate due to a use-after-free (UAF) issue in the Linux kernel's gpio-virtuser implementation.

2

How do I fix CVE-2026-23158?

To fix CVE-2026-23158, you should update your Linux kernel to the latest version where the vulnerability has been patched.

3

What systems are affected by CVE-2026-23158?

CVE-2026-23158 affects Linux kernel versions that include the gpio-virtuser implementation.

4

What could happen if CVE-2026-23158 is exploited?

Exploitation of CVE-2026-23158 could lead to system crashes or arbitrary code execution due to the use-after-free vulnerability.

5

When was CVE-2026-23158 disclosed?

CVE-2026-23158 was disclosed in the first half of 2026 after the vulnerability was resolved in the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203