# CVE-2026-64492: iio: temperature: tmp006: use devm_iio_trigger_register

> A use-after-free vulnerability in the Linux kernel tmp006 temperature sensor driver allows local attackers to cause a system crash or potentially execute code during module unload.

- **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:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-64492, DEBIAN-CVE-2026-64492, GHSA-fg54-gxf9-gvmv, ROOT-OS-UBUNTU-2204-CVE-2026-64492, UBUNTU-CVE-2026-64492

## What is CVE-2026-64492?

CVE-2026-64492 is an use after free 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: temperature: tmp006: use devm_iio_trigger_register

tmp006_probe() allocates the DRDY trigger with devm_iio_trigger_alloc()
but registers it with plain iio_trigger_register(). The driver has no
.remove() callback, so on module unload the trigger stays in the global
trigger list while its memory is freed by devm, leaving a dangling
entry.

Switch to devm_iio_trigger_register() so the registration is undone in
the same devm scope as the allocation.

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


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

Apply the vendor's patch.

## Is CVE-2026-64492 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64492 is an use after free 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-64492 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-64492/ (Markdown: https://insights.sbomify.com/CVE-2026-64492/index.md)
```

## Sources

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

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