CVE-2026-72141
Description
A flaw was found in the Linux kernel's i2c-imx driver. A malicious device on the I2C bus or a local attacker with access to the I2C bus could exploit this vulnerability by initiating an SMBus block-read operation with a zero byte count. This can cause the I2C bus to become locked, requiring a power cycle of the controller to restore functionality, leading to a Denial of Service (DoS).
Statement
This flaw is rated as Low severity because successful exploitation requires specialized NXP i.MX hardware architectures and either local access to the bus or physical access to an attached bus device. Standard enterprise server deployments on typical architectures are not affected as the driver is specific to i.MX platforms. Even on vulnerable hardware, the blast radius is confined to a denial of service on the impacted bus controller, causing it to lock up until power-cycled, with no exposure to unauthorized data disclosure or system compromise.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | 7.5 |
| Attack Vector | Local | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Integrity,Availability
Technical Impact: Modify Application Data; DoS: Instability; DoS: Crash, Exit, or Restart
When a resource is not properly locked, an attacker could modify the resource while it is being operated on by the product. This might violate the product's assumption that the resource will not change, potentially leading to unexpected behaviors.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.