Menu

Star on GitHub · 3.2k

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()…

Published Jul 25, 2026EPSS 0.21%

Overview

CVE-2026-64492 is a known-severity vulnerability. It was published on July 25, 2026.

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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-64492?

CVE-2026-64492 is a known-severity vulnerability. It was published on July 25, 2026.

How severe is CVE-2026-64492?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-64492?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64492?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64492 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.