Answer in brief
CVE-2026-89934 records a Unknown severity vulnerability in iio: light: ltrf216a: fix runtime PM reference leak in error path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=83f0bcd40d5cf88870d2f2bb8b97c772b92a3d1f <c4f003d8578f5718fe1ec332bc89f9ff69fd205b || >=83f0bcd40d5cf88870d2f2bb8b97c772b92a3d1f <0614928a3eda35bddd8c2f02311e286b59bbe746 || >=83f0bcd40d5cf88870d2f2bb8b97c772b92a3d1f <80e7381e8cccb543397572af153865f34aaf4353 || >=83f0bcd40d5cf88870d2f2bb8b97c772b92a3d1f <c132aef0e757a39036b1d40faf0569f2e343b13e | c4f003d8578f5718fe1ec332bc89f9ff69fd205b, 0614928a3eda35bddd8c2f02311e286b59bbe746, 80e7381e8cccb543397572af153865f34aaf4353, c132aef0e757a39036b1d40faf0569f2e343b13e |
| Linux/Linuxgeneric | 6.1 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
In the Linux kernel, the following vulnerability has been resolved: iio: light: ltrf216a: fix runtime PM reference leak in error path ltrf216a_get_lux() acquires a runtime PM reference by calling ltrf216a_set_power_state(data, true). However, if ltrf216a_read_data() fails, the function returns immediately without dropping the reference. This leaves the runtime PM usage count unbalanced, preventing the device from autosuspending after a failed read. Fix this by releasing the runtime PM reference before returning from the error path.
Quoted source text, attributed separately from HOL analysis.