CVE-2025-38425: i2c: tegra: check msg length in SMBUS block read
i2c: tegra: check msg length in SMBUS block read
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.142 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.95 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.35 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.15.4 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1 - Compensating control
In the Linux kernel i2c: tegra SMBUS block-read handling, stop reading when the device-provided message length is 0 or greater than the maximum allowed number of bytes.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38425?
CVE-2025-38425 has been assessed as having a moderate severity level due to potential denial of service implications.
How do I fix CVE-2025-38425?
To fix CVE-2025-38425, ensure that your Linux kernel is updated to the latest version where the vulnerability has been patched.
What does CVE-2025-38425 affect?
CVE-2025-38425 affects the SMBUS block read functionality within the Linux kernel.
Can CVE-2025-38425 be exploited remotely?
CVE-2025-38425 requires local access to exploit, as it pertains to a device communication protocol.
Is there a workaround for CVE-2025-38425?
There are no known workarounds for CVE-2025-38425 other than applying the recommended kernel updates.