LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver crash issue affecting systems that use TI INA2xx power-sensor devices through device tree configuration. A specific compatible-string combination can make the driver dereference a NULL pointer during probe. Business impact is most likely device startup failure or local denial of service on affected embedded or appliance platforms.

Executive priority

Treat as targeted operational risk for embedded Linux products, not a broad enterprise emergency. Patch during the next maintenance window unless affected devices crash during boot or provide critical monitoring.

Technical view

The ina2xx IIO ADC driver can receive a NULL struct i2c_device_id during probe when OF matching falls back from an undeclared compatible string, such as ti,ina232, to ti,ina231. The fix uses the already populated driver type data instead of the potentially NULL ID pointer and adds a generic name in the config table.

Likely exposure

Exposure appears limited to Linux systems with the ina2xx driver and relevant device tree entries for TI INA2xx-family power sensors. General-purpose servers without this hardware or driver path are unlikely to be affected.

Exploitation context

The source bundle does not show KEV listing, public exploitation, exploit code, or remote attack evidence. The described trigger is configuration and hardware-context dependent, involving device tree matching during driver initialization.

Researcher notes

Evidence is source-level and specific: a NULL pointer arises from OF/I2C modalias mismatch in ina2xx probe handling. No CVSS, CWE, or exploitation details are provided, so severity confidence is constrained.

Mitigation direction

  • Update to a Linux kernel or vendor kernel containing the referenced stable fixes.
  • Check distribution or device vendor advisories for the correct fixed build.
  • Review affected embedded device trees for INA2xx compatible-string combinations.
  • Prioritize appliances where sensor initialization failure affects boot or monitoring.

Validation and detection

  • Inventory systems using the Linux ina2xx IIO ADC driver.
  • Inspect device trees for ti,ina232 with ti,ina231 fallback entries.
  • Confirm kernel source or changelog includes a referenced stable fix commit.
  • Test affected hardware boots and probes the sensor without kernel NULL dereference.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53834 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc43a102e67db99c8bfe6e8a9280cec13ff53b789, c43a102e67db99c8bfe6e8a9280cec13ff53b789, c43a102e67db99c8bfe6e8a9280cec13ff53b789, c43a102e67db99c8bfe6e8a9280cec13ff53b789unaffected
LinuxLinux4.5, 0, 5.15.127, 6.1.46, 6.4.11, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.