Live › vulnerability › CVE-2026-98971
Go to dashboardIn the Linux kernel's Exar GPIO driver, a failed cleanup registration makes the probe path release ID 0 instead of the device's own allocated ID. An attacker is not described as gaining code execution or data access; the flaw can leak an ID and free an ID belonging to another device.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
gpio: exar: initialize the ID before registering its cleanup
devm_add_action_or_reset() invokes the cleanup action immediately when registering the action fails. gpio_exar_probe() currently stores the allocated ID in exar_gpio only after registering the action, so that failure makes exar_devm_ida_free() release ID 0. If the allocated ID is nonzero, this leaks that ID and can free ID 0 belonging to another device.
Store the ID before registering the cleanup action so both the immediate failure path and normal device teardown release the correct allocation.
This page as .md · .json · in your agent: get_signal("CVE-2026-98971")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.