CVE-2026-98657: Linux kernel · iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e462b47b9637b8c0285f4a38b5af9a322847d164 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e462b47b9637b8c0285f4a38b5af9a322847d164, 20ebd7f4e35c0a737f011bc83aeb0cdd37507648, 06fa13c53442257b94ea1519555ceddaaea57e0d +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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().
References
- git.kernel.org/stable/c/2c8211eef98929c5188f8c2224e83b9a63b41bd1 (opens in a new tab)
- git.kernel.org/stable/c/06fa13c53442257b94ea1519555ceddaaea57e0d (opens in a new tab)
- git.kernel.org/stable/c/20ebd7f4e35c0a737f011bc83aeb0cdd37507648 (opens in a new tab)
- git.kernel.org/stable/c/e462b47b9637b8c0285f4a38b5af9a322847d164 (opens in a new tab)
- git.kernel.org/stable/c/4daa9ca557b4b98ae1ad38a6d1deaa3e31eb8edf (opens in a new tab)