CVE-2026-43005 hwmon: (tps53679) Fix array access with zero-length block read

High 7.1 Published Updated

A zero-length I2C read in the TPS53679 hardware monitoring driver causes an out-of-bounds stack read, potentially leaking kernel memory or crashing the system.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-43005?

CVE-2026-43005 is a high-severity memory corruption vulnerability in Linux kernel, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

In the Linux kernel, the following vulnerability has been resolved:

hwmon: (tps53679) Fix array access with zero-length block read

i2c_smbus_read_block_data() can return 0, indicating a zero-length read. When this happens, tps53679_identify_chip() 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".

Weakness: CWE-125

Which versions are affected by CVE-2026-43005?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-43005?

Apply the vendor's patch.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-43005 being exploited?

There is no known exploitation of CVE-2026-43005 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2026-43005, DEBIAN-CVE-2026-43005, GHSA-5x7p-776c-f64j, UBUNTU-CVE-2026-43005.

Is CVE-2026-43005 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free