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.
Covered by Rapid7
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade linux | Dec 10, 2025 | Dec 10, 2025 |
| Ubuntu | — | Upgrade linux-xilinx-zynqmpUpgrade linux-intel-iotgUpgrade linux-intel-iotg-5.15Upgrade linux-oracle-5.15Upgrade linux-realtimeUpgrade linux-hwe-5.15Upgrade linux-raspiUpgrade linux-oracleUpgrade linux-kvmUpgrade linux-azureUpgrade linux-lowlatencyUpgrade linux-bluefieldUpgrade linux-lowlatency-hwe-5.15Upgrade linux-gcp-5.15Upgrade linux-nvidiaUpgrade linux-aws-5.15Upgrade linux-gkeUpgrade linux-riscv-5.15Upgrade linux-gcpUpgrade linux-intel-iot-realtimeUpgrade linuxUpgrade linux-nvidia-tegra-igxUpgrade linux-ibmUpgrade linux-nvidia-tegra-5.15Upgrade linux-azure-5.15Upgrade linux-awsUpgrade linux-gkeopUpgrade linux-ibm-5.15Upgrade linux-nvidia-tegra | Dec 11, 2025 | Dec 9, 2025 |
Prioritise with Active Threat Intelligence
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub