{"id":"CVE-2026-99718","summary":"hwmon: (peci/dimmtemp) Fix devres leak and UAF on concurrent unbind","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (peci/dimmtemp) Fix devres leak and UAF on concurrent unbind\n\nWhen a peci_dimmtemp device is unbound concurrently with its delayed\ninitialization work (detect_work), newly allocated devm resources and\nthe hwmon device are leaked, leading to a use-after-free when reading\nthe lingering hwmon sysfs attributes.\n\nIn peci_dimmtemp_probe(), detect_work is registered for cancellation via\ndevm_delayed_work_autocancel(). During driver detach, devres_release_all()\nfirst moves all existing entries from dev-\u003edevres_head onto a local todo\nlist before invoking their release callbacks in reverse order. If\ncreate_dimm_temp_info_delayed() is already running when\ndevm_delayed_work_drop() calls cancel_delayed_work_sync(),\ncreate_dimm_temp_info() can allocate dimmtemp_label strings via\ndevm_kzalloc()/devm_kasprintf() and register the hwmon device via\ndevm_hwmon_device_register_with_info(), appending new devres entries to\nthe now-empty dev-\u003edevres_head. Once the work finishes,\ndevres_release_all() frees priv and priv-\u003ename from the local todo list\nwithout re-evaluating dev-\u003edevres_head, leaving the late devres\nallocations and registered hwmon device behind with a dangling priv\npointer.\n\nCancel detect_work synchronously in a driver .remove() callback instead\nof relying on devm_delayed_work_autocancel() so that the work is fully\ndrained before devres_release_all() detaches dev-\u003edevres_head, allowing\nany devm resources registered by the delayed work to be released in\nproper reverse order. Also only schedule detect_work when\ncheck_populated_dimms() returns -EAGAIN so that probe failure paths do\nnot leave delayed work pending.","modified":"2026-11-20T07:01:12.728714693Z","published":"2026-11-20T05:50:56.106Z","database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99718.json","cna_assigner":"Linux"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/3f6bd7aeea5c3bd5ced9e23184155065f551ea96"},{"type":"WEB","url":"https://git.kernel.org/stable/c/61bc4514b8e99e9733c04de028885f6fc906d628"},{"type":"WEB","url":"https://git.kernel.org/stable/c/c7dcea6bdc6c36c649c1fdd29909b232bcac28c9"},{"type":"WEB","url":"https://git.kernel.org/stable/c/f27cb64b04af01370fbe2d23ba9aeb3401d6def8"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99718.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99718"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"73bc1b885daeb684fbcd16cc4e979cac6a831b12"},{"fixed":"f27cb64b04af01370fbe2d23ba9aeb3401d6def8"},{"fixed":"c7dcea6bdc6c36c649c1fdd29909b232bcac28c9"},{"fixed":"3f6bd7aeea5c3bd5ced9e23184155065f551ea96"},{"fixed":"61bc4514b8e99e9733c04de028885f6fc906d628"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99718.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.18.0"},{"fixed":"6.12.118"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.64"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.3.5"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99718.json"}}],"schema_version":"1.9.2"}