CVE-2026-98657 Linux CVE debrief

Who should care

Defenders responsible for Linux kernel-based systems, especially those using pulsedlight proximity devices, should assess exposure and prioritize patching. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify Linux kernel versions, review system configurations, and monitor for potential use-after-free issues related to iio devices.

Why it matters

Defenders should prioritize patching and verifying Linux kernel versions for the iio: proximity: pulsedlight driver vulnerability to prevent potential use-after-free issues and exposure.

• Potential use-after-free issues related to iio devices
• Sysfs/chardev nodes remaining live and pointing to freed memory
• Verification of patched versions required for affected systems
• Inventory checks necessary for pulsedlight proximity device usage

Technical summary

The Linux kernel's iio: proximity: pulsedlight driver has a vulnerability that can cause an iio_device to be left registered on PM setup failure. This occurs when pm_runtime_set_active() fails in probe(), causing the function to jump to error_unreg_buffer, which only calls iio_triggered_buffer_cleanup() without undoing the successful iio_device_register() call. As a result, the iio core still has the device registered, and the sysfs/chardev nodes remain live, pointing to freed memory. This vulnerability can lead to potential use-after-free issues and exposure in systems using the affected Linux kernel versions and pulsedlight proximity devices.

Defensive priority

Defenders should prioritize verifying and applying patches for this vulnerability, especially for systems using the affected Linux kernel versions and pulsedlight proximity devices.

Recommended defensive actions

• Verify and apply patches for the Linux kernel's iio: proximity: pulsedlight driver vulnerability
• Review system configurations and inventory for potential exposure
• Monitor for potential use-after-free issues related to iio devices
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in the Linux kernel's iio: proximity: pulsedlight driver, which can cause an iio_device to be left registered on PM setup failure. However, the corpus lacks specific information on affected versions, exploitation, or victim data. Defenders should verify Linux kernel versions, review system configurations, and monitor for potential use-after-free issues related to iio devices. The official CVE Program record and NIST NVD detail page offer source-provided CVE metadata and

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.