# CVE-2023-53834: iio: adc: ina2xx: avoid NULL pointer dereference on OF device match

> A local attacker with specific hardware configuration can cause a kernel crash via NULL pointer dereference in the INA2xx ADC driver.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-53834, DEBIAN-CVE-2023-53834, GHSA-vwr3-mpmm-8xqx, ROOT-OS-DEBIAN-11-CVE-2023-53834, UBUNTU-CVE-2023-53834

## What is CVE-2023-53834?

CVE-2023-53834 is a vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

iio: adc: ina2xx: avoid NULL pointer dereference on OF device match

The affected lines were resulting in a NULL pointer dereference on our
platform because the device tree contained the following list of
compatible strings:

    power-sensor@40 {
        compatible = "ti,ina232", "ti,ina231";
        ...
    };

Since the driver doesn't declare a compatible string "ti,ina232", the OF
matching succeeds on "ti,ina231". But the I2C device ID info is
populated via the first compatible string, cf. modalias population in
of_i2c_get_board_info(). Since there is no "ina232" entry in the legacy
I2C device ID table either, the struct i2c_device_id *id pointer in the
probe function is NULL.

Fix this by using the already populated type variable instead, which
points to the proper driver data. Since the name is also wanted, add a
generic one to the ina2xx_config table.

## Which versions are affected by CVE-2023-53834?


## How do I fix CVE-2023-53834?

Apply the vendor's patch.

## Is CVE-2023-53834 being exploited?

There is no known exploitation of CVE-2023-53834 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-53834 and fix it if it is affected.

What it is: CVE-2023-53834 is a vulnerability in Linux, published on 9 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-53834 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-53834/ (Markdown: https://insights.sbomify.com/CVE-2023-53834/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-53834
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-53834
- OSV: https://osv.dev/vulnerability/CVE-2023-53834

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-53834/
Summaries are generated and may contain mistakes; the official description above is the record.