CVE-2026-98679: iio: accel: kxcjk-1013: reject duplicate event disable
iio: accel: kxcjk-1013: reject duplicate event disable
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.113-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.10-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.10.273 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.15.224 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.113 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.56 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.10 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1
Event History
Frequently Asked Questions
What action triggers the runtime PM usage-count underflow?
A repeated write that disables an IIO event when that event is already disabled can call the power-state routine again without a corresponding runtime PM reference. This can produce a "Runtime PM usage count underflow" warning.
Are repeated event-enable requests affected in the same way?
No. The driver already ignores repeated enable requests; the issue is specifically repeated disable requests.
How can I identify a system that may already have encountered this issue?
Check kernel logs for a "Runtime PM usage count underflow" warning in connection with the kxcjk-1013 accelerometer driver, particularly after duplicate writes to an event-enable attribute.
What mitigation is available if the fix cannot be deployed immediately?
Avoid issuing duplicate disable writes to the affected IIO event-enable attribute. Ensure event configuration changes only write a disabled state when the event is currently enabled.