LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23158 is a Linux kernel memory safety bug in the gpio-virtuser configfs cleanup path. A device object can be freed before its mutex guard finishes, causing a use-after-free. The public record does not provide CVSS, impact details, or evidence of exploitation.

Executive priority

Treat this as a kernel maintenance priority, not an emergency based on current evidence. Raise priority for multi-user Linux systems, embedded fleets, or environments that use gpio-virtuser/configfs paths, because kernel memory safety issues can have serious impact if reachable.

Technical view

The release function destroys and frees the gpio-virtuser device while still inside a guard(mutex) scope. When the guard cleanup runs, it calls mutex_unlock on freed memory, producing a slab use-after-free. The fix limits the lock scope so unlock occurs before mutex_destroy and kfree.

Likely exposure

Exposure appears limited to Linux kernels that include the vulnerable gpio-virtuser code and affected version ranges or commits listed by the CVE record. The sources do not identify affected distributions, default configurations, or whether the vulnerable path is commonly reachable.

Exploitation context

No provided source reports active exploitation, public exploit code, or KEV listing. The available information describes a kernel use-after-free during configfs release handling, but does not establish practical exploitability, required privileges, or remote attack surface.

Researcher notes

Evidence is limited to the CVE text and Linux stable commit references. Key unknowns are reachability, privilege requirements, exploitability, distribution impact, and whether common kernel builds include the vulnerable feature. Avoid assuming remote exposure or privilege escalation without additional vendor analysis.

Mitigation direction

  • Apply Linux stable or distribution kernel updates containing the referenced fixes.
  • Check vendor kernel advisories for backported fixes and affected package versions.
  • Prioritize systems using gpio-virtuser or configfs-related testing and GPIO workflows.
  • If patch timing is constrained, follow vendor guidance for temporary risk reduction.

Validation and detection

  • Inventory running kernel versions across servers, appliances, and build images.
  • Compare deployed kernels with the affected versions and referenced fixed commits.
  • Check whether gpio-virtuser functionality is present or used in the environment.
  • Confirm distribution packages include the upstream stable fix or a documented backport.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23158 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux91581c4b3f29e2e22aeb1a62e842d529ca638b2d, 91581c4b3f29e2e22aeb1a62e842d529ca638b2d, 91581c4b3f29e2e22aeb1a62e842d529ca638b2dunaffected
LinuxLinux6.11, 0, 6.12.69, 6.18.9, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.