VulnerabilityPublished 25 Jul 2026Updated 9 Nov 2026

CVE-2026-64492: Linux kernel · iio: temperature: tmp006: use devm_iio_trigger_register

Affects Linux kernelSource GCVE Database

Compare

Authoritative record:CVE-2026-64492· Medium

Not known to be exploited · fixed in 7.0.0-1012.12~24.04.1 : update Linux kernel when convenient.

Data as of 9 Nov 2026, 15:34 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Patch: Available – fixed in 7.0.0-1012.12~24.04.1, 7.0.0-1014.14~24.04.1, 7.0.0-1013.13~24.04.1 +14

Exploitation 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 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Patches and advisories

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected <7.0.0-31.31	Fixed in 7.0.0-31.31
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected <7.0.0-1012.12	Fixed in 7.0.0-1012.12
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected <7.0.0-1013.13	Fixed in 7.0.0-1013.13
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected <7.0.0-1011.11	Fixed in 7.0.0-1011.11
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected <7.0.0-1006.7	Fixed in 7.0.0-1006.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and has been applied in Linux kernel versions 7.0.0-1012.12~24.04.1 and later. Users should update to these fixed versions or later to remediate the issue. No additional mitigation is required beyond applying the official fix.

Description

A vulnerability in the Linux kernel's iio temperature driver (tmp006) was identified where the driver improperly registers a trigger, leading to a dangling pointer on module unload. This occurs because the trigger is allocated with devm_iio_trigger_alloc() but registered with iio_trigger_register(), and the driver lacks a .remove() callback to unregister it. The issue has been fixed by switching to devm_iio_trigger_register(), ensuring proper cleanup within the device-managed scope.

Impact

The vulnerability could lead to a dangling pointer in kernel memory after module unload, which may cause system instability or crashes. The severity is rated low, and there is no indication of exploitation in the wild or privilege escalation directly linked to this flaw.

Summary

The Linux kernel's tmp006 temperature sensor driver allocates a data-ready (DRDY) trigger using devm_iio_trigger_alloc() but registers it using iio_trigger_register(). Since the driver does not implement a .remove() callback, unloading the module leaves the trigger registered globally while its memory is freed, resulting in a dangling entry. The fix replaces iio_trigger_register() with devm_iio_trigger_register(), which ties the registration lifecycle to the device-managed memory scope, preventing the dangling pointer issue.

References

Community reviews

Loading reviews…