CVE-2026-43005: hwmon: (tps53679) Fix array access with zero-length block read
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (tps53679) Fix array access with zero-length block read
i2csmbusreadblockdata() can return 0, indicating a zero-length read. When this happens, tps53679identifychip() accesses buf[ret - 1] which is buf[-1], reading one byte before the buffer on the stack.
Fix by changing the check from "ret < 0" to "ret <= 0", treating a zero-length read as an error (-EIO), which prevents the out-of-bounds array access.
Also fix a typo in the adjacent comment: "if present" instead of duplicate "if".
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-nvidiato a version that resolves this vulnerability.Fixed in 7.0.0-1006.6 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.19.12-1 - 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.116-1Fixed in 7.2.15-1Fixed in 7.3.4-1 - Compensating control
In the Linux kernel hwmon tps53679 driver, change the check in tps53679_identify_chip() from "ret < 0" to "ret <= 0", treating a zero-length i2c_smbus_read_block_data() result as an error (-EIO) to prevent the buf[ret - 1] out-of-bounds access.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43005?
CVE-2026-43005 is considered to be a moderate severity vulnerability affecting the Linux kernel.
How do I fix CVE-2026-43005?
To fix CVE-2026-43005, update your Linux kernel to the latest version where the vulnerability has been resolved.
What components are affected by CVE-2026-43005?
CVE-2026-43005 affects the hwmon subsystem, specifically the tps53679 driver in the Linux kernel.
What are the potential impacts of CVE-2026-43005?
The potential impacts of CVE-2026-43005 include incorrect handling of zero-length block reads, which could lead to system instability.
Is there a workaround for CVE-2026-43005?
There are no known workarounds for CVE-2026-43005; updating the kernel is the recommended mitigation.