Bug 2555191 (CVE-2026-98657) - CVE-2026-98657 kernel: iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure
Summary: CVE-2026-98657 kernel: iio: proximity: pulsedlight: fix iio_device left regis...
Keywords:
Status: NEW
Alias: CVE-2026-98657
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-18 15:59 UTC by OSIDB Bzimport
Modified: 2026-10-21 21:19 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-18 15:59:57 UTC
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().


Note You need to log in before you can comment on or make changes to this bug.