CVE-2023-53834

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

N/A
Published: December 9, 2025 at 01:29 AM UTC
Updated: June 17, 2026 at 06:46 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.5 ≤ v < 5.15.1274.5 ≤ v < 6.1.464.5 ≤ v < 6.4.114.5 ≤ v < 6.54.5c43a102e67db99c8bfe6e8a9280cec13ff53b789
Vendor states this is fixed in 13f3ce53b65aa8b44cad7039d31e62c9ffd6c5d1 (fixed)
Vendor states this is fixed in 77b689cc27d489b75d33f1a368356d70eb0ce08c (fixed)
Vendor states this is fixed in a41e19cc0d6b6a445a4133170b90271e4a2553dc (fixed)
Vendor states this is fixed in a8e2ae6296d56478fb98ae7f739846ed121f154f (fixed)
Vendor states this is fixed in 4.5 (unaffected)
Vendor states this is fixed in 5.15.127 (unaffected)
Vendor states this is fixed in 6.1.46 (unaffected)
Vendor states this is fixed in 6.4.11 (unaffected)
Vendor states this is fixed in 6.5 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card