Answer in brief
CVE-2026-64492 records a Unknown severity vulnerability in iio: temperature: tmp006: use devm_iio_trigger_register. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=91f75ccf9f032e17cde54f0c01eae2da4f067bc5 <a4f8491da9563ba6eb77969ac26fc7052114c476 || >=91f75ccf9f032e17cde54f0c01eae2da4f067bc5 <d90f868f56a16e10eedc6552f48d99dff4d275b7 || >=91f75ccf9f032e17cde54f0c01eae2da4f067bc5 <3c5eed894efd93d68d7f6a359a81ddef0e928774 | a4f8491da9563ba6eb77969ac26fc7052114c476, d90f868f56a16e10eedc6552f48d99dff4d275b7, 3c5eed894efd93d68d7f6a359a81ddef0e928774 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64492 records a Unknown severity vulnerability in iio: temperature: tmp006: use devm_iio_trigger_register. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=91f75ccf9f032e17cde54f0c01eae2da4f067bc5 <a4f8491da9563ba6eb77969ac26fc7052114c476 || >=91f75ccf9f032e17cde54f0c01eae2da4f067bc5 <d90f868f56a16e10eedc6552f48d99dff4d275b7 || >=91f75ccf9f032e17cde54f0c01eae2da4f067bc5 <3c5eed894efd93d68d7f6a359a81ddef0e928774 | a4f8491da9563ba6eb77969ac26fc7052114c476, d90f868f56a16e10eedc6552f48d99dff4d275b7, 3c5eed894efd93d68d7f6a359a81ddef0e928774 |
| Linux/Linuxgeneric | 6.13 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.