AZL-115585: CVE-2026-99718 affecting package kernel 6.6.161.1-1
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (peci/dimmtemp) Fix devres leak and UAF on concurrent unbind
When a pecidimmtemp device is unbound concurrently with its delayed initialization work (detectwork), newly allocated devm resources and the hwmon device are leaked, leading to a use-after-free when reading the lingering hwmon sysfs attributes.
In pecidimmtempprobe(), detectwork is registered for cancellation via devmdelayedworkautocancel(). During driver detach, devresreleaseall() first moves all existing entries from dev->devreshead onto a local todo list before invoking their release callbacks in reverse order. If createdimmtempinfodelayed() is already running when devmdelayedworkdrop() calls canceldelayedworksync(), createdimmtempinfo() can allocate dimmtemplabel strings via devmkzalloc()/devmkasprintf() and register the hwmon device via devmhwmondeviceregisterwithinfo(), appending new devres entries to the now-empty dev->devreshead. Once the work finishes, devresreleaseall() frees priv and priv->name from the local todo list without re-evaluating dev->devreshead, leaving the late devres allocations and registered hwmon device behind with a dangling priv pointer.
Cancel detectwork synchronously in a driver .remove() callback instead of relying on devmdelayedworkautocancel() so that the work is fully drained before devresreleaseall() detaches dev->devreshead, allowing any devm resources registered by the delayed work to be released in proper reverse order. Also only schedule detectwork when checkpopulateddimms() returns -EAGAIN so that probe failure paths do not leave delayed work pending.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
For hwmon (peci/dimmtemp), cancel detect_work synchronously in the driver .remove() callback instead of relying on devm_delayed_work_autocancel(), so the work is fully drained before devres_release_all().