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

Greg Kroah-Hartman <[email protected]> Sat, 25 Jul 2026 10:51:49 +0200
Newsgroups org.kernel.vger.linux-cve-announce
Message-ID <2026072550-CVE-2026-64492-5ec8@gregkh>
From: Greg Kroah-Hartman <[email protected]>

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.

The Linux kernel CVE team has assigned CVE-2026-64492 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.13 with commit 91f75ccf9f032e17cde54f0c01eae2da4f067bc5 and fixed in 6.18.39 with commit a4f8491da9563ba6eb77969ac26fc7052114c476
	Issue introduced in 6.13 with commit 91f75ccf9f032e17cde54f0c01eae2da4f067bc5 and fixed in 7.1.4 with commit d90f868f56a16e10eedc6552f48d99dff4d275b7
	Issue introduced in 6.13 with commit 91f75ccf9f032e17cde54f0c01eae2da4f067bc5 and fixed in 7.2-rc1 with commit 3c5eed894efd93d68d7f6a359a81ddef0e928774

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-64492
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/iio/temperature/tmp006.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/a4f8491da9563ba6eb77969ac26fc7052114c476
	https://git.kernel.org/stable/c/d90f868f56a16e10eedc6552f48d99dff4d275b7
	https://git.kernel.org/stable/c/3c5eed894efd93d68d7f6a359a81ddef0e928774