CVE-2023-52627

What it actually does

Missing event configuration callbacks in the ad7091r IIO driver cause a null pointer dereference when userspace attempts to read, write, enable, or disable ADC threshold events on AD7091R-5 devices.

Why it matters to the business

Systems using affected Linux kernels with AD7091R-5 ADCs may experience unexpected crashes or denial of service when event configuration is attempted, increasing downtime risk on embedded or industrial deployments until patched.

How an attack unfolds

An attacker with local access or the ability to interact with the IIO sysfs interface triggers event configuration operations on an AD7091R-5 device; the kernel follows unset function pointers, dereferences null, and panics.

How to fix it

Update the Linux kernel to a version containing commit 1eba6f7ffa295a0eec098c107043074be7cc4ec5 or later; rebuild and deploy the updated kernel image on all affected systems.

How to confirm the fix worked

Verify the running kernel contains commit 1eba6f7ffa295a0eec098c107043074be7cc4ec5 by checking /proc/version or kernel build logs; confirm event callbacks are present in the ad7091r-base module via source inspection or symbol checks.

Typical attack path

1. Identify host running vulnerable kernel with ad7091r-5 driver loaded
2. Locate IIO device sysfs entries for AD7091R-5
3. Write to event threshold or enable files via sysfs or libiio
4. Kernel dereferences null callback and crashes

How to detect it

Search kernel logs and dmesg for oops or panic messages containing ad7091r, iio_event, or null pointer dereference during event configuration; review audit logs for unexpected writes to IIO event sysfs attributes on systems with the driver loaded.

What your security team should do

• Prioritize kernel update on any system exposing AD7091R-5 hardware to untrusted users
• Audit IIO device usage and restrict sysfs access where possible until patched
• Monitor for kernel oops reports referencing ad7091r or iio events