CVE-2026-64492: Linux kernel · iio: temperature: tmp006: use devm_iio_trigger_register
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 3 Nov 2026, 19:14 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
AI-suggested
A fix is available that replaces iio_trigger_register() with devm_iio_trigger_register() in the tmp006 driver to ensure proper resource cleanup. Users should update to a Linux kernel version that includes this fix once released. No additional mitigation is required beyond applying the official patch.
Description
A vulnerability in the Linux kernel's tmp006 temperature sensor driver was fixed by changing the trigger registration method. The driver allocated a data-ready (DRDY) trigger with devm_iio_trigger_alloc() but registered it with iio_trigger_register(), which did not properly unregister the trigger on module unload. This caused a dangling pointer in the global trigger list after the memory was freed. The fix involved switching to devm_iio_trigger_register() to ensure proper cleanup within the same device-managed scope.