Bug 2507178 (CVE-2026-64492)

Summary: CVE-2026-64492 kernel: iio: temperature: tmp006: use devm_iio_trigger_register
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: rhel-process-autobot, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the Linux kernel's `tmp006` temperature sensor driver. This vulnerability occurs because the driver incorrectly handles the registration and de-registration of a hardware trigger. When the module is unloaded, a pointer to freed memory remains active, creating a 'dangling pointer'. This can lead to system instability or potentially allow an attacker to cause a denial of service.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-07-25 10:09:09 UTC 
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.
Comment 1 TEJ RATHI 2026-07-29 13:31:53 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026072550-CVE-2026-64492-5ec8@gregkh/T