CVE-2026-43356
Received Received - Intake
NULL Pointer Dereference in Linux Kernel IIO IMU ADIS Driver

Publication date: 2026-05-08

Last updated on: 2026-05-08

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: iio: imu: adis: Fix NULL pointer dereference in adis_init The adis_init() function dereferences adis->ops to check if the individual function pointers (write, read, reset) are NULL, but does not first check if adis->ops itself is NULL. Drivers like adis16480, adis16490, adis16545 and others do not set custom ops and rely on adis_init() assigning the defaults. Since struct adis is zero-initialized by devm_iio_device_alloc(), adis->ops is NULL when adis_init() is called, causing a NULL pointer dereference: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 pc : adis_init+0xc0/0x118 Call trace: adis_init+0xc0/0x118 adis16480_probe+0xe0/0x670 Fix this by checking if adis->ops is NULL before dereferencing it, falling through to assign the default ops in that case.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-08
Last Modified
2026-05-08
Generated
2026-05-09
AI Q&A
2026-05-08
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's iio: imu: adis driver, specifically in the adis_init() function. The function attempts to dereference a pointer called adis->ops to check if certain function pointers (write, read, reset) are NULL. However, it does not first verify whether adis->ops itself is NULL.

Because the struct adis is zero-initialized, adis->ops can be NULL when adis_init() is called, leading to a NULL pointer dereference and a kernel crash.

The issue affects drivers like adis16480, adis16490, adis16545, and others that do not set custom ops and rely on adis_init() to assign default operations.

The fix involves checking if adis->ops is NULL before dereferencing it, and if it is NULL, assigning the default operations.


How can this vulnerability impact me? :

This vulnerability can cause a NULL pointer dereference in the Linux kernel, leading to a kernel crash or system instability when affected drivers are initialized.

Such crashes can result in denial of service, potentially disrupting normal operation of systems using the affected drivers.


What immediate steps should I take to mitigate this vulnerability?

The vulnerability is caused by a NULL pointer dereference in the adis_init() function of the Linux kernel's iio imu adis driver. The fix involves checking if adis->ops is NULL before dereferencing it and assigning default operations if it is NULL.

To mitigate this vulnerability immediately, you should update your Linux kernel to a version that includes this fix.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart