iio: temperature: tmp006: use devm_iio_trigger_register
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.397.1.47.2In 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.
From the CVE record · Linux
The tmp006 temperature driver registers a trigger without arranging for its removal when the module unloads. Unloading the module frees the trigger while leaving a dangling entry in the global trigger list. The input does not specify an attacker action, authentication requirement, or user interaction needed to exploit this condition.
Engineers running Linux kernels with the tmp006 temperature driver should check whether their kernel includes the fix; affected versions are not specified.