# CVE-2026-64499: iio: adc: ti-ads1119: fix PM reference leak in buffer preenable

> A reference leak in the TI ADS1119 ADC driver can cause the device to remain runtime-active indefinitely, leading to resource exhaustion and denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-64499, DEBIAN-CVE-2026-64499, GHSA-jrf5-24f4-rfq7, ROOT-OS-UBUNTU-2204-CVE-2026-64499, UBUNTU-CVE-2026-64499

## What is CVE-2026-64499?

CVE-2026-64499 is a denial of service vulnerability in Linux, published on 25 Jul 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:

iio: adc: ti-ads1119: fix PM reference leak in buffer preenable

ads1119_triggered_buffer_preenable() resumes the device with
pm_runtime_resume_and_get() before starting a conversion.

If i2c_smbus_write_byte() fails, the function returns the error directly
and leaves the runtime PM usage counter elevated. The matching
postdisable callback is not called when preenable fails, so the reference
is leaked and the device may remain runtime-active indefinitely.

Store the I2C transfer result in ret and drop the runtime PM reference on
failure before returning the error.

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


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

Apply the vendor's patch.

## Is CVE-2026-64499 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64499 is a denial of service vulnerability in Linux, published on 25 Jul 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-64499 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-64499/ (Markdown: https://insights.sbomify.com/CVE-2026-64499/index.md)
```

## Sources

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

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