# CVE-2026-74685: hwmon: (ltc4282) Clamp negative current limits

> A local attacker with high privileges can trigger an integer overflow in the LTC4282 hardware monitoring driver, causing incorrect current limit settings.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2026
- **Updated:** 22 Aug 2026
- **Also known as:** BELL-CVE-2026-74685, DEBIAN-CVE-2026-74685, GHSA-pg82-jq9q-m7pf, UBUNTU-CVE-2026-74685

## What is CVE-2026-74685?

CVE-2026-74685 is a vulnerability in Linux, published on 22 Aug 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: (ltc4282) Clamp negative current limits

When a negative value is passed to ltc4282_write_curr(), the signed long
val is cast directly to u64:

drivers/hwmon/ltc4282.c:ltc4282_write_curr() {
        /* need to pass it in millivolt */
        u32 in = DIV_ROUND_CLOSEST_ULL((u64)val * st->rsense, DECA * MICRO);
        ...
}

This cast converts negative inputs into large positive values. The
subsequent division result overflows the u32 in variable, truncating
to a pseudo-random positive value. When this is passed to
ltc4282_write_voltage_byte(), it is clamped to the maximum limit instead
of zero.

Clamp val to 0 and to the maximum supported upper limit before the cast
and assign the result to a 64-bit temporary variable before the division
to avoid the underflow and an also possible overflow.

## Which versions are affected by CVE-2026-74685?


## How do I fix CVE-2026-74685?

Apply the vendor's patch.

## Is CVE-2026-74685 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74685 and fix it if it is affected.

What it is: CVE-2026-74685 is a vulnerability in Linux, published on 22 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74685 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74685/ (Markdown: https://insights.sbomify.com/CVE-2026-74685/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74685
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74685
- OSV: https://osv.dev/vulnerability/CVE-2026-74685

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74685/
Summaries are generated and may contain mistakes; the official description above is the record.