CVE-2026-23158

{"id": "CVE-2026-23158", "cveTags": [], "metrics": {}, "published": "2026-02-14T16:15:55.967", "references": [{"url": "https://git.kernel.org/stable/c/53ad4a948a4586359b841d607c08fb16c5503230", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/7bec90f605cfb138006f5ba575f2310593347110", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/815a8e3bf72811d402b30bd4a53cde5e9df7a563", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Awaiting Analysis", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ngpio: virtuser: fix UAF in configfs release path\n\nThe gpio-virtuser configfs release path uses guard(mutex) to protect\nthe device structure. However, the device is freed before the guard\ncleanup runs, causing mutex_unlock() to operate on freed memory.\n\nSpecifically, gpio_virtuser_device_config_group_release() destroys\nthe mutex and frees the device while still inside the guard(mutex)\nscope. When the function returns, the guard cleanup invokes\nmutex_unlock(&dev->lock), resulting in a slab use-after-free.\n\nLimit the mutex lifetime by using a scoped_guard() only around the\nactivation check, so that the lock is released before mutex_destroy()\nand kfree() are called."}, {"lang": "es", "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\ngpio: virtuser: corregir uso despu\u00e9s de liberaci\u00f3n en la ruta de liberaci\u00f3n de configfs\n\nLa ruta de liberaci\u00f3n de configfs de gpio-virtuser usa guard(mutex) para proteger la estructura del dispositivo. Sin embargo, el dispositivo es liberado antes de que se ejecute la limpieza del guard, causando que mutex_unlock() opere sobre memoria liberada.\n\nEspec\u00edficamente, gpio_virtuser_device_config_group_release() destruye el mutex y libera el dispositivo mientras a\u00fan est\u00e1 dentro del \u00e1mbito de guard(mutex). Cuando la funci\u00f3n retorna, la limpieza del guard invoca mutex_unlock(&dev->lock), resultando en un uso despu\u00e9s de liberaci\u00f3n de slab.\n\nLimitar la vida \u00fatil del mutex usando un scoped_guard() solo alrededor de la verificaci\u00f3n de activaci\u00f3n, para que el bloqueo sea liberado antes de que se llamen a mutex_destroy() y kfree()."}], "lastModified": "2026-02-18T17:52:44.520", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}