CVE-2026-89933: iio: pressure: dps310: fix NULL pointer dereference on ACPI probe

Published Sep 16, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

iio: pressure: dps310: fix NULL pointer dereference on ACPI probe

When the device is enumerated through its ACPI HID (IFX3100), i2cclientgetdeviceid() returns NULL: the ACPI-derived client name does not match the driver's i2cdeviceid table. dps310probe() then dereferences that NULL pointer in "iio->name = id->name" and crashes the kernel during probe.

The IIO device name is always "dps310", so set it directly and drop the now-unused device-id lookup.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Update the dps310 IIO driver probe code to assign the IIO device name directly to "dps310" instead of setting it via iio->name = id->name after i2c_client_get_device_id() returns NULL during ACPI enumeration.

    Linux kernel IIO driver (dps310) iio device name assignment = Set iio device name directly to "dps310"; remove reliance on ACPI HID-derived device id name (drop i2c_device_id table lookup).

Event History

Sep 16, 2026
CVE Published
via MITRE·10:32 AM
Data Sourced
via MITRE·10:32 AM
Description

Frequently Asked Questions

1

Which systems are exposed to this crash?

Systems using the DPS310 pressure sensor driver are exposed when the device is enumerated through the ACPI HID IFX3100. In that path, the ACPI-derived client name does not match the driver's I2C device-ID table.

2

What is required to trigger the issue?

The vulnerable probe path is reached when an IFX3100 device is probed through ACPI. No additional attacker-controlled input or permissions are described; the reported outcome is a kernel crash during driver probe.

3

How can I tell whether a system has encountered the vulnerability?

Affected systems crash during DPS310 driver probing because dps310_probe() dereferences a NULL device-ID pointer. The relevant deployment condition is ACPI enumeration using HID IFX3100.

4

What changes in the resolved code?

The fix sets the IIO device name directly to "dps310" rather than obtaining it from the I2C device-ID lookup. This avoids dereferencing the NULL result returned for the ACPI-enumerated device.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203