Live › vulnerability › CVE-2026-98657
Go to dashboardWhen the PulsedLight lidar driver's probe fails during power management setup, the kernel leaves the IIO device registered after its memory is freed. Local code or a user with access to the sysfs or chardev nodes could reach freed memory.
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.
Unknown from the sources.
Unknown from the sources.
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:
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().
This page as .md · .json · in your agent: get_signal("CVE-2026-98657")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.