Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98657iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure

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

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 12 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 4ac4e086fd8c59e6b69089e6f7605500b63a6d17 – < 93ecee9ff3af4c2b482fdd4ec98c3308e8dd23a6
    • affected 4ac4e086fd8c59e6b69089e6f7605500b63a6d17 – < 58e68e5272a319fff4a704df1ac41e9e3c69587c
    • affected 4ac4e086fd8c59e6b69089e6f7605500b63a6d17 – < 4a564e39cb99234e8c5b0a39aa30edcc8cf4cf1b
    • affected 4ac4e086fd8c59e6b69089e6f7605500b63a6d17 – < 2c8211eef98929c5188f8c2224e83b9a63b41bd1
    • affected 4ac4e086fd8c59e6b69089e6f7605500b63a6d17 – < 06fa13c53442257b94ea1519555ceddaaea57e0d
    • affected 4ac4e086fd8c59e6b69089e6f7605500b63a6d17 – < 20ebd7f4e35c0a737f011bc83aeb0cdd37507648
    • affected 4ac4e086fd8c59e6b69089e6f7605500b63a6d17 – < e462b47b9637b8c0285f4a38b5af9a322847d164
    • affected 4ac4e086fd8c59e6b69089e6f7605500b63a6d17 – < 4daa9ca557b4b98ae1ad38a6d1deaa3e31eb8edf
  • Linux · Linux

    • affected 4.5
    • unaffected < 4.5
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.56 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98657 badge
[![CVE-2026-98657](https://cveledger.app/badge/CVE-2026-98657.svg)](https://cveledger.app/cve/CVE-2026-98657)

Record last updated .