CVE-2026-64492

Unknown

Last modified

CVE-2026-64492 is a vulnerability of currently unknown severity. 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..

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 91f75ccf9f032e17cde54f0c01eae2da4f067bc5, < a4f8491da9563ba6eb77969ac26fc7052114c476; >= 91f75ccf9f032e17cde54f0c01eae2da4f067bc5, < d90f868f56a16e10eedc6552f48d99dff4d275b7; >= 91f75ccf9f032e17cde54f0c01eae2da4f067bc5, < 3c5eed894efd93d68d7f6a359a81ddef0e928774
LinuxLinux6.13

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-64492?
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.
How severe is CVE-2026-64492?
Severity scoring for CVE-2026-64492 is pending analysis.
How do I fix CVE-2026-64492?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-64492?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST