CVE-2026-98657

UnknownEPSS 0.17%

Last modified

CVE-2026-98657 is a vulnerability of currently unknown severity. 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().. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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().

Metrics

EPSS Probability
0.17%

6.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 4ac4e086fd8c59e6b69089e6f7605500b63a6d17, < 93ecee9ff3af4c2b482fdd4ec98c3308e8dd23a6; >= 4ac4e086fd8c59e6b69089e6f7605500b63a6d17, < 58e68e5272a319fff4a704df1ac41e9e3c69587c; >= 4ac4e086fd8c59e6b69089e6f7605500b63a6d17, < 4a564e39cb99234e8c5b0a39aa30edcc8cf4cf1b; >= 4ac4e086fd8c59e6b69089e6f7605500b63a6d17, < 2c8211eef98929c5188f8c2224e83b9a63b41bd1; >= 4ac4e086fd8c59e6b69089e6f7605500b63a6d17, < 06fa13c53442257b94ea1519555ceddaaea57e0d; >= 4ac4e086fd8c59e6b69089e6f7605500b63a6d17, < 20ebd7f4e35c0a737f011bc83aeb0cdd37507648; >= 4ac4e086fd8c59e6b69089e6f7605500b63a6d17, < e462b47b9637b8c0285f4a38b5af9a322847d164; >= 4ac4e086fd8c59e6b69089e6f7605500b63a6d17, < 4daa9ca557b4b98ae1ad38a6d1deaa3e31eb8edf
LinuxLinux4.5

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98657?
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().
How severe is CVE-2026-98657?
Severity scoring for CVE-2026-98657 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-98657?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-98657?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST